Skip to content

feat: Update weaviate to 1.16.0 and weaviate client to 3.9#734

Closed
dirkkul wants to merge 1 commit intodocarray:chore-benchmark-refactor-298from
dirkkul:chore-benchmark-refactor-298-update-weaviate
Closed

feat: Update weaviate to 1.16.0 and weaviate client to 3.9#734
dirkkul wants to merge 1 commit intodocarray:chore-benchmark-refactor-298from
dirkkul:chore-benchmark-refactor-298-update-weaviate

Conversation

@dirkkul
Copy link
Copy Markdown
Contributor

@dirkkul dirkkul commented Nov 8, 2022

Goals:

This updates weaviate and weaviate-python-client to the latest version which include many speedups. Moreover multithreading of the client is enabled for the benchmarking.

  • update weaviate server and weaviate client
  • update some python client calls to include class names
  • update some of the tests
  • update documentation

Note: I work for weaviate/SeMi

columns: Optional[Union[List[Tuple[str, str]], Dict[str, str]]] = None
distance: Optional[str] = None
# weaviate python client parameters
batch_size: Optional[int] = field(default=50)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure if these parameters should be here in config, or should be passed as kwargs in the relevant methods.

@samsja @JohannesMessner @alaeddine-13 what is the pattern in other cases?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think for batch_size it's always been in config.
The reason is we use batch_size in extend which handles batching for users.
We don't expose the parameter in extend's interface.

@dirkkul dirkkul force-pushed the chore-benchmark-refactor-298-update-weaviate branch from 4ea16bf to 21ca6cd Compare November 8, 2022 15:18
@dirkkul
Copy link
Copy Markdown
Contributor Author

dirkkul commented Nov 8, 2022

I will split this into two PRs, where one targets main and another one targeting the benchmarking PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants