Tim Fox
Tim Fox
If a query is cancelled from the CLI (e.g. CTRL-C) or client connection is closed, we must make the query is cancelled on the server.
Currently we cancel an MV or index fill if a leadership election occurs concurrently. This is because fill must occur on the processor and leadership election causes processor to migrate...
* Processor batch size * Forward writes batch size * Num concurrent server requests per connection * Remoting buffer sizes
Currently drop source/mv doesn't complete until all data is dropped. And during that time the DDL lock is held so no other DDL can be executed. This can take a...
Right now, the the initial state and MV fill batch sizes and the row processor max batch sizes are not configurable. We should make them configurable.
We should keep track of the number of rows in a source or materialized view so users don't have to create expensive 'count(*)' materialized views to track this. It can...
Which should print available commands. Then also should be able to do help to get more detailed info.
Should show the topic info for the source and the query for the MV
To latest version
Our current metrics coverage is quite sparse. It could be improved.