-
Notifications
You must be signed in to change notification settings - Fork 313
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
Add support for vector tiles API #1652
Comments
The main blocker for this issue is migrating to version 8.x of the Python client in #1350 as version 7.14 of the Elasticsearch Python client does not support that API. Support was added in 7.15.0: https://www.elastic.co/guide/en/elasticsearch/client/python-api/7.17/release-notes.html#rn-7-15-0. This API is quite specific in that it returns binary data, so it could make sense to wait for the upgrade, which hopefully should be done in March. |
@craigtaverner @iverase We released Rally 2.8.0 last month with the 8.x client. Are you still interested in doing that? |
Yes we are super interested, need to find the time (and in my case, some python skills :)) |
Can you maybe write how such an operation would look in a Rally track, so that we can see how difficult it would be to implement? Some runners are only a few lines of code. |
A mvt request is very similar to a search request except it requires 4 mandatory parameters. One is the field where the geo data is, and the other three is the actual tile to be processed by providing the Therefore a simple example would look like:
|
An example of how this would look like in the geoshape track is:
or another example:
|
It would be great if we could add operations in rally that points to the vector tiles API. It currently fails because the result of the query is a protbuffer that the system does not understand.
The text was updated successfully, but these errors were encountered: