Marqo

Latest version: v3.9.1

Safety actively analyzes 682244 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 11

2.10.2

Bug fixes and minor changes
- Fix an issue where CUDA was not automatically selected as the default device for the `embed` endpoint, even when available [941](https://github.com/marqo-ai/marqo/pull/941).

2.10.1

Bug fixes and minor changes
- Improve the clarity of the error message when Marqo can not download the provided image ([905](https://github.com/marqo-ai/marqo/pull/905)).
- Improve the error message in hybrid search to avoid confusion ([900](https://github.com/marqo-ai/marqo/pull/900)).
- Fix a bug where a `500` error is returned when an unsupported search method is provided. Marqo now correctly returns a `400` error ([899](https://github.com/marqo-ai/marqo/pull/899)).
- Fix a bug where a `500` error is returned when an invalid image URL with non-ASCII characters is provided. Marqo now encodes the image URL correctly ([908](https://github.com/marqo-ai/marqo/pull/908)).

2.10.0

New features

- Hybrid Search (`"searchMethod": "HYBRID”`) (https://github.com/marqo-ai/marqo/pull/845). Marqo now supports hybrid search, combining lexical and tensor search (using reciprocal rank fusion) to provide the best relevance possible. See usage [here](https://docs.marqo.ai/2.10/API-Reference/Search/search/#hybrid-parameters).
- Lexical Search score modifiers (https://github.com/marqo-ai/marqo/pull/884). Score modifiers are now supported for lexical search. Score modifiers are applied on all matches, not just the top k retrieved, resulting in more relevant hits. See usage [here](https://docs.marqo.ai/2.10/API-Reference/Search/search/#score-modifiers).

Bug fixes and minor changes

- Increase unstructured index default `filterStringMaxLength` to 50, from 20 (https://github.com/marqo-ai/marqo/pull/887). Maximum length of string fields to be used in query filters now defaults to 50 characters long.

Contributor shout-outs

- Huge shoutout to all our 4.3k stargazers! We’ve come a long way as a team and as a community, so a huge thanks to everyone who continues to support Marqo.
- Feel free to keep on sharing questions and feedback on our [forum](https://community.marqo.ai/) and [Slack channel](https://marqo-community.slack.com/join/shared_invite/zt-2b4nsvbd2-TDf8agPszzWH5hYKBMIgDA#/shared-invite/email)! If you have any more inquiries or thoughts, please don’t hesitate to reach out.

2.9.0

New features
- Numeric map data type. Add numeric map data types, available for filtering and score modification ([851](https://github.com/marqo-ai/marqo/pull/851)). You can now store a map/dictionary of numeric value and use these in your filters and score modifiers, or simply retrieve these with your documents. See the new types [here](https://docs.marqo.ai/2.9/API-Reference/Indexes/create_structured_index/?h=struct#fields). For usage in search, see [here](https://docs.marqo.ai/2.9/API-Reference/Search/search/?h=map#example_4). This is supported only for indexes created with Marqo 2.9 or later.
- Double and long score modifier fields. Support double and long in map and standard numeric fields for score modifiers in both structured and unstructured indexes ([851](https://github.com/marqo-ai/marqo/pull/851)). You can now use double values with full precision as score modifiers, as well as integers with guaranteed precision up to `2^53 - 1` (increased from `2^24 - 1`), with only negligible precision loss for larger values. For details on these new types, see the documentation [here](https://docs.marqo.ai/2.9/API-Reference/Indexes/create_structured_index/?h=struct#fields).

Bug fixes and minor changes
- Fix the bug in score modifiers where missing score modifiers in docs used in `multiply_score_by` lead to the multiplication of scores by `0` instead of by `1` ([851](https://github.com/marqo-ai/marqo/pull/851)).
- Improve upgrade stability ([874](https://github.com/marqo-ai/marqo/pull/874)). Fix failure of state transfer between some versions of Marqo due to Vespa binaries being copied with state. For more information, see the documentation [here](https://docs.marqo.ai/2.9/Guides/Advanced-Usage/transferring_state/?h=transfer)
- Improve the model warmup strategy on instances with CUDA ([877](https://github.com/marqo-ai/marqo/pull/877)). Marqo now requires less memory to warmup the models when spinning up .
- Improve create/delete index resilience to partial failures ([866](https://github.com/marqo-ai/marqo/pull/866)). You can now bring Marqo to a consistent state by repeating the operation until getting a `200` response.

Contributor shout-outs
- Shoutouts to our valuable 4.3k stargazers!
- Thanks a lot for the discussion and suggestions in our community. We love to hear your thoughts and requests. Join our [Slack channel](https://join.slack.com/t/marqo-community/shared_invite/zt-2jm456s90-1pFxdE5kDQt5imqddXUIcw) and [forum](https://community.marqo.ai/) now.

2.8.2

Bug fixes and minor changes
- Fix an issue in Marqo where loading some models (e.g., `open_clip/xlm-roberta-base-ViT-B-32/laion5b_s13b_b90k`) is unsuccessful.
This was resolved by upgrading the `transformers` and `optimum` packages. ([868](https://github.com/marqo-ai/marqo/pull/868))

2.8.1

Bug fixes and minor changes
- Fix a bug in Marqo where a 500 error is returned for the entire batch of documents when encountering an invalid document ID during image downloading.
Marqo now correctly returns an error and rejects the invalid document,
allowing successful indexing of other valid documents with a 200 response. ([860](https://github.com/marqo-ai/marqo/pull/860))

Page 3 of 11

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.