Luqum

Latest version: v0.13.0

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

Scan your dependencies

Page 3 of 4

0.7.2

===================

Fixed
-----

- adding the `zero_terms_query` to `match_phrase` was a mistake (introduced in 0.7.0).

Added
-----

- 0.7.0 introduced the `match` query for queries with single words on analyzed fields,
whereas before it was using `match_phrase`.
Although this is more coherent,
this may cause difficulties on edge cases
as this may leads to results different from previous release.

This behaviour might be disabled using a new `match_word_as_phrase` parameter
to `luqum.elasticsearch.visitor.ElasticsearchQueryBuilder`.
Note that this parameter maybe removed in future release.
(the `field_options` might be used instead on a per field basis).

0.7.1

==================

Fixed
-----

- version introduced because of a bad upload on pypi (Restructured description error)

0.7.0

==================

Added
-----

- Support for named queries (see `elastic named queries`__)
- Helper to automatically create ElasticSearch query builder options from the index configuration,
see: `luqum.elasticsearch.schema`
- a new arg `field_options` on `luqum.elasticsearch.visitor.ElasticsearchQueryBuilder`
allows to add parameters to field queries.
It also permits to control the type of query for match queries.
- now for a query with a single word, if the field is analyzed,
the transformation to elastic search query will use a "match" query instead of a "match_phrase".
This is more conform in behaviour to what the expression of "query_string" would produce.


Fixed
-----

- small fix in utils.TreeTransformerV2,
which was not removing elements from lists or tuple as stated
- single word matches, are now `match`, and not `match_phrase`
- `match_phrase` has the `zero_terms_query` field, as for `match`

__ https://www.elastic.co/guide/en/elasticsearch/reference/current/search-request-named-queries-and-filters.html

Changed
--------

- dropped official Python 3.3 support

0.6.0

==================

Added
-----

- Manage object fields in elasicsearch transformation

Fixed
-----

- minor fix, getting better error message when parsing error is at the end of content

Changed
--------

- better handling of nested fields may lead to shorter requests

0.5.3

==================

Added
-----

- A class to transform smartly replace implicit operations with explicit one (*OR* or *AND*)

Fixed
-----

- handling of fields names with numbers followed by a number
(better handling of time in expressions)

Changed
-------

- now using ply 3.10

0.5.2

==================

Changed
-------

- better recursion in the tree transformer util (API Change)

Fixed
-----

- handling of empty phrases for elasticsearch query builder

Page 3 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.