.NET event sourcing library with CosmosDB, DynamoDB, EventStoreDB, message-db, SqlStreamStore and integration test backends. Focused at stream level; see https://github.com/jet/propulsion for cross-stream projections/subscriptions/reactions
-o/--output filepath: emit CR-delimited JSON showing raw query output
-P: pretty print the output indented over multiple lines
-m/--mode raw: SELECT * from matching docs (and show ages)
-sn: specify exact stream name instead of category name or category pattern
Example use cases:
Useful complement to eqx dump for troubleshooting (eqx query focuses on the raw JSON and uses CosmosDB queries; eqx dump does a read Equivalent to an application-level Query call)
Great for gathering event counts/RU cost stats for tuning/sanity checking
Also useful for shuffling categories or streams between stores for inspection and/or doing general things that you do via SELECT INTO hackery in SQL stores
the propulsion-indexer template's upconvert and sync commands and/or the propulsion-sync templates can be used to import and/or upconvert based on such dumps (NOTE they can of course also identically work from the changefeed)
Adds features to
eqx query ... cosmos:-C: emit query output to Console-o/--output filepath: emit CR-delimited JSON showing raw query output-P: pretty print the output indented over multiple lines-m/--mode raw:SELECT *from matching docs (and show ages)-sn: specify exact stream name instead of category name or category patternExample use cases:
eqx dumpfor troubleshooting (eqx queryfocuses on the raw JSON and uses CosmosDB queries;eqx dumpdoes a read Equivalent to an application-levelQuerycall)SELECT INTOhackery in SQL storespropulsion-indexertemplate'supconvertandsynccommands and/or thepropulsion-synctemplates can be used to import and/or upconvert based on such dumps (NOTE they can of course also identically work from the changefeed)