-
Notifications
You must be signed in to change notification settings - Fork 4
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
Adapt to v2.0.0 core #19
base: master
Are you sure you want to change the base?
Conversation
89b41e3
to
182f45d
Compare
182f45d
to
15a7caa
Compare
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.
Thank you for porting this to 2.0 :)
Main comment is a question about sharding etc, would this be removed by the PR as it is now?
Maybe another question is if it makes sense to generalize the Executors implemented here and provide them as standalone Executors?
with f: | ||
f.index(inputs=DocumentArray([d1, d2, d3])) | ||
|
||
with Flow.load_config( |
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.
Do we need this file in the PR? Looks like some local test to me which will not be used in the actual stress test? If you think its handy to have as some local test entry point, maybe generalize this and otherwise remove?
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.
@jacobowitz this will be removed after flow runs successfully, only for test purpose, shouldn't commit to the PR, good catch!
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.
thx for your review.
This PR is still in local progress.
pods: | ||
- name: segmenter | ||
polling: any | ||
shards: {{ JINA_SEGMENTER_SHARDS }} |
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.
why are we removing the sharding? Testing this as part of the stress test is one of the added values here I think?
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.
same as above
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.
Maybe I should convert this PR to a draft one.
Let me fix the status of this PR.
@niuzs-alan things needs to be done (from the flow/executor level):
|
@bwanglzu