Closed clairewood closed 10 months ago
It looks like a behavior change that came with upgrading clap versions. I noticed it while adding avro support, but I didn't catch the change in behavior for casing.
Basically, clap won't parse things by --<id>
with our current version, and when you switch to the short flags, which do work, the code is retrieving them using uppercase versions of the ids.
Thank you so much for your help and fixing this so quickly! :)
Closing this for #146
Apologies if this ends up being my own error/misunderstanding, I'm very new here!
I'm working on getting kafka-delta-ingest up and running locally, but when I try following the "Starting Worker Processes" steps in the Using Azure Event Hubs section of the README, I get "unexpected argument" errors.
When I try running it as it appears in the README:
When I try running it with a space between the dashes and the argument IDs, I get the same error but with this line changed slightly:
error: unexpected argument 'allowed_latency' found
When I change the order of the argument IDs, it gives me the error for whichever one is first.When I use the short argument IDs (like "-k" or "-a"), it stops giving me unexpected argument errors, but gives me a different error instead:
I have also tried following the steps in the README for Using Azure Event Hubs in order to connect my existing Kafka stream (in an Event Hub instance) to a delta table (in ADLS) but I'm getting the same exact errors.
Is anyone else experiencing this issue with the argument IDs? Is the documentation outdated and I should be trying something else? Or did I do something wrong in setup (forking and cloning the repo in VS Code then just following the steps in the readme)?
Any help would be hugely appreciated. Thank you!