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
DHC 0.29.0 introduced a known breaking change the requires upgrading to deephaven-java-client-barrage-dagger:0.29.0. This is captured here: #192.
After upgrading Benchmark to use the new barrage dagger version, a problem was discovered with table snapshots where a table name and column names could be retrieved through the barrage client that contained no rows. Below are the tickets capturing that issue for deephaven-core.
A workaround was offered that is more like the fetchDuration support in Benchmark. This is stated to be more efficient and looks cleaner that the broken way of doing snapshots.
From Nate's investigation: I appear to be able to reproduce. A work around is to use BarrageSession#subscribe (instead of snapshot) and then invoke snapshotEntireTable instead of entireTable (or snapshotPartialTable if that is what you are doing).
DHC 0.29.0 introduced a known breaking change the requires upgrading to deephaven-java-client-barrage-dagger:0.29.0. This is captured here: #192.
After upgrading Benchmark to use the new barrage dagger version, a problem was discovered with table snapshots where a table name and column names could be retrieved through the barrage client that contained no rows. Below are the tickets capturing that issue for deephaven-core.
A workaround was offered that is more like the fetchDuration support in Benchmark. This is stated to be more efficient and looks cleaner that the broken way of doing snapshots.
From Nate's investigation:
I appear to be able to reproduce. A work around is to use BarrageSession#subscribe (instead of snapshot) and then invoke snapshotEntireTable instead of entireTable (or snapshotPartialTable if that is what you are doing).
BarrageSession
Subscription/Snapshot Methods now ReturnFuture<Table>
deephaven-core#4676The text was updated successfully, but these errors were encountered: