I made the necessary fixes to remove the deprecated Throwables.propagate
calls. However, I need a committer to review.
https://issues.apache.org/jira/browse/CASSANDRA-14218
Thank you,
Claude
engage in
discussion it’s unclear to me what advantage this encoding scheme brings. It
might be worth outlining what algorithmic advantage you foresee for what data
distributions in which collection types.
On 6 Sep 2022, at 07:16, Claude Warren via dev wrote:
I am just learning the ropes
but no one impedes us to also have 3) if
we get to have projected views. However, I think that projected
views is a new general-purpose feature with its own complexities,
so it would deserve its own CEP, if someone is willing to work on
the implementation.
On Wed, 31 Aug 2
efficiency improvement. The CEP guidelines say a CEP is encouraged “for
significant user-facing or changes that cut across multiple subsystems”. Any
reason why a Jira isn’t sufficient?
Abe
On Sep 5, 2022, at 1:57 AM, Claude Warren via dev
wrote:
I have just posted a CEP covering an Enhancement
I have just posted a CEP covering an Enhancement for Sparse Data
Serialzation. This is in response to CASSANDRA-8959
I look forward to responses.
I like this approach. However, in light of some of the discussions on
view and the like perhaps the function is (column value as returned by
select ) + 42
So a null counter column becomes 0 before the update calculation is applied.
Then any null can be considered null unless addressed by IfN
Is there enough support here for VIEWS to be the implementation strategy
for displaying masking functions?
It seems to me the view would have to store the query and apply a where
clause to it, so the same PK would be in play.
It has data leaking properties.
It has more use cases as it can be
