-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Query crawler #686
base: main
Are you sure you want to change the base?
Query crawler #686
Conversation
@bugout-dev check
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reconsidered crawler architecture.
logger = logging.getLogger(__name__) | ||
|
||
|
||
def parser_queries_execute_handler(args: argparse.Namespace) -> None: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After discussing with @kompotkot and @Andrei-Dolgolev:
We realized that we want this crawler to go through the Query API like any other user would.
The plan is to remove this mooncrawl/queries_crawler
code and update the Moonstream Python client to provide this functionality similarly to how we used it in autocorns biologist
:
https://github.com/bugout-dev/autocorns/blob/cf00fb492de254821730a256d238d5a332810db6/autocorns/biologist.py#L371
We can remove the existing Moonstream Python client, bump the client version, and publish the new client.
We need to cherry pick from this PR later. |
Although we will not use The We will revisit this after our current batch of urgent work. |
Changes
Fetch query from journal, validate query, execute query and push to bucket if required.
How to test these changes?
Tested locally
Related issues