feat: First stab at urwid UI & async #170
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Features / Changes
clickhouse-connectas it's no longer neededBreaking Changes
Refactors several configuration variables:
num_batchesis renamed tonum_xapi_batchesto clarify it's scopenum_workersis added and requiredcsv_load_from_s3_afteris renamed toload_from_s3_afteras it is now shared with the CHDB backendRefactors backend names, the available backends are now:
Removes the
load_db_from_s3command in favor of a new--load_db_onlyflag onload_dbthat fulfills the same behaviorTodo
Testing
num_batchestonum_xapi_batchesand addingnum_workers: 4xapi-db-load ui --config_file <path to your config>xapi-db-load load_db --config_file <path to your config>should still workThe new CHDB backend writes lz4 compressed ClickHouse native files to S3 then optionally loads them to ClickHouse by running insert commands on ClickHouse, similar to how the CSV backend works. However it does not currently support writing the files anywhere but S3.