This release is a pre-release and may not be stable for production use.
AtlasQ
AtlasQ allows the usage of AtlasSearch keeping the MongoEngine syntax.
Structure
The package tries to follow the MongoEngine structure;
the major differences reside in the transform.py and queryset.py files.
Transform
Like in MongoEngine, a step in the pipeline is the creation of a query from a Q object:
we have to find a correspondence between the MongoEngine common syntax and what AtlasSearch allows.
For doing this, we had to find some compromises.
Not every keyword is supported at the moment: if you have an actual use case that you would like to support, please be free to open an issue or a PR at any moment.
QuerySet
There are probably a thousand of better implementation, if you actually knew MongoEngine and above all PyMongo. Unfortunately, our knowledge is limited, so here we go. If you find a solution that works better, again, feel free to open an issue or a PR.
The main idea, is that the filter should work like an aggregation.
For doing so, and with keeping the compatibility on how MongoEngine works (i.e. the filter should return a queryset of Document) we had to do some work.
Calling .aggregate instead has to work as MongoEngine expect, meaning a list of dictionaries.
Usage
Now the most important part: how do you use this package?
from mongoengine import Document, fields
from atlasq import AtlasManager, AtlasQ, AtlasQuerySet
index_name = str("my_index")
class MyDocument(Document):
name = fields.StringField(required=True)
surname = fields.StringField(required=True)
atlas = AtlasManager(index_name)
obj = MyDocument.objects.create(name="value", surname="value2")
qs = MyDocument.atlas.filter(name="value")
assert isinstance(qs, AtlasQuerySet)
obj_from_atlas = qs.first()
assert obj == obj_from_atlas
obj2_from_atlas = MyDocument.atlas.get(AtlasQ(name="value") & AtlasQ(surname="value2"))
assert obj == obj2_from_atlas
obj3_from_atlas = MyDocument.atlas.get(AtlasQ(wrong_field="value"))
assert obj3_from_atlas is None
Extended Features
Validation
We also decided to have, optionally, a validation of the index. Two things are checked:
- The index actually exists (If you query a non-existing index, Atlas as default behaviour will not raise any error).
- The fields that you are querying are actually indexed(If you query a field that is not indexed, Atlas as default behaviour will not raise any error, and will return an empty list).
To make these check, you need to call the function
ensure_indexon the queryset.
from mongoengine import Document, fields
from atlasq import AtlasManager, AtlasQ
index_name = str("my_index")
class MyDocument(Document):
name = fields.StringField(required=True)
surname = fields.StringField(required=True)
atlas = AtlasManager(index_name)
result = MyDocument.atlas.ensure_index("user", "pwd", "group", "cluster")
assert result is True
obj1_from_atlas = MyDocument.atlas.get(AtlasQ(name="value"))
obj2_from_atlas = MyDocument.atlas.get(AtlasQ(wrong_field="value")) # raises AtlasIndexFieldError
EmbeddedDocuments
Embedded documents are queried in two different ways, depending on how you created your Search Index.
Remember to ensure the index so that AtlasQ can know how your index is defined
If you used the embeddedDocuments type, AtlasQ will use the embeddedDocument query syntax.
Otherwise, if you used the document type, or you did not ensure the index, a normal text search with the . syntax will be used.
Upload index
It is possible to upload directly the Search index using AtlasQ, calling the function upload_index on the queryset. Syntax checks on the index itself are performed.
If the _id is not present but pk or id was specified, it will be automatically added, allowing valid text query on the
primary key.
from mongoengine import Document, fields
from atlasq import AtlasManager
index_name = str("my_index")
index = {
"analyzer": "lucene.keyword",
"mappings": {
"dynamic": False,
"fields": {
"_id": {
"type": "objectId"
},
"name": {
"type": "string"
},
"surname": {
"type": "string"
},
}
}
}
class MyDocument(Document):
name = fields.StringField(required=True)
surname = fields.StringField(required=True)
atlas = AtlasManager(index_name)
result = MyDocument.atlas.ensure_index("user", "pwd", "group", "cluster")
assert result is False
MyDocument.atlas.upload_index(index, "user", "pwd", "group", "cluster")
result = MyDocument.atlas.ensure_index("user", "pwd", "group", "cluster")
assert result is True
Metadata
Release files for atlasq-tschaume 0.11.1.dev2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| atlasq-tschaume-0.11.1.dev2.tar.gz | 38.1 kB | Without provenance | Details for atlasq-tschaume-0.11.1.dev2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| atlasq_tschaume-0.11.1.dev2-py3-none-any.whl | Python 3 | none | any | Details for atlasq_tschaume-0.11.1.dev2-py3-none-any.whl |
Total release size: 53.8 kB
Release files / atlasq-tschaume-0.11.1.dev2.tar.gz
| Download URL | atlasq-tschaume-0.11.1.dev2.tar.gz |
|---|---|
| Size | 38.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9393356edebae037b1b47e16d73a7a04969451eaa3e38f1bdc20d1d9b08ece68
|
|
BLAKE2b-256 checksum How to use checksums |
8c5f91e3d9c1712c8e235c95c86eeb265bb106802f5bcbe334e28f605f55b018
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.3
|
Release files / atlasq_tschaume-0.11.1.dev2-py3-none-any.whl
| Download URL | atlasq_tschaume-0.11.1.dev2-py3-none-any.whl |
|---|---|
| Size | 15.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f38813972c8c379964f09200fa89f9ae909ccbf5b3483bb6a77d5bf34720dde0
|
|
BLAKE2b-256 checksum How to use checksums |
a58c83b96f52f5a5b8e418bf4cbf9089cfbea33fc0b809c28fd5a9b9393b67ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.3
|
Security for atlasq-tschaume 0.11.1.dev2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.