You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cc8d364 refactored the plumbing around (un)persist for Table, MatrixTable and BlockMatrix.
It had the slightly undesirable effect of breaking persist on BlockMatrix.
Version
0.2.114
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
)
This change is split out from a larger refactoring effort on the various
Backend
implementations. The goals of this effort are to provide query-level
configuration to the backend that's currently tied to the lifetime of a
backend,
reduce code duplication and reduce state duplication.
In this change, I'm removing blockmatrix persist/unpersist from the
`Backend`
interface by adding `BlockMatrixCache: mutable.Map[String, BlockMatrix]`
to
`ExecuteContext`. The various reader/writer implementations simply fetch
the
block matrix from this cache. For the spark backend, this is backed by a
cache
whose lifetime is tied to the spark backend. Since block matrices are
not
supported in the local and service backends, the cache is an empty map.
Note that block matrix persist is broken in python (hail-is#14689)
What happened?
cc8d364 refactored the plumbing around (un)persist for
Table
,MatrixTable
andBlockMatrix
.It had the slightly undesirable effect of breaking persist on
BlockMatrix
.Version
0.2.114
Relevant log output
No response
The text was updated successfully, but these errors were encountered: