> it sounds like you’re saying users who actually use the profiler today are
> SOL and need to roll their own solution.
No, I am saying it’s good to have sidecar expose this and expose common
patterns that people actually use.
If sidecar wishes to expose exec and take the fact that this API c
A few thoughts here:
1) Run-time configuration (or even compile-time inclusion/exclusion?) that
allows you to enable/disable the “raw” mode in both Cassandra and Sidecar would
be a reasonable middle-ground here. I’m not crazy about exposing it by default
though, so I’d a minimum have it default
In the second option, we use the repair timestamp to re-update any cell or
row we want to fix in the base table. This approach is problematic because
it alters the write time of user-supplied data. Although Cassandra does not
allow users to set timestamps for LWT writes, users may still rely on the
easy-cass-lab has a few shell functions that I use often they're defined
as c-flame* [1]
The arguments I've found most useful have been -X for excluding Parked
threads, -I for narrowing scope to particular callstacks (compaction), -e
for switching between allocation / cpu / wall profiling, -o for
> Sorry, Blake—I was traveling last week and couldn’t reply to your email
> sooner.
No worries, I’ll be taking some time off soon as well.
> I don’t think the first or second option is ideal. We should treat the base
> table as the source of truth. Modifying it—or forcing an update on it, even
