Update rest-api-spec main #3019
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
github-actions
bot
requested review from
Anaethelion,
ezimuel,
flobernd,
JoshMock,
l-trotta,
miguelgrinberg,
picandocodigo,
pquentin,
srikanthmanvi,
swallez and
technige
| @@ -0,0 +1,28 @@ | |||
| { | |||
| "ingest.delete_ip_location_database": { | |||
There was a problem hiding this comment.
@joegallo I'm slightly confused by those new APIs. Based on https://github.com/elastic/elasticsearch/pull/114548/files#diff-e691792ba34345b9c60eac06a6730438c8265376839f01e598b4f02e39f8a1ac, my understanding is that right now they are strictly equivalent to the GeoIP APIs. Will they do something different at some point? When should we expose them to clients and serverless docs?
There was a problem hiding this comment.
In the eventual future, the geoip APIs will be deprecated and removed (there is no plan to do this at the moment, but given the fullness of time it will happen 'one day'), but the ip_location APIs will stay around forever. In the near and intermediate term, it's the same behavior available under two names.
github-actions
bot
force-pushed
the
automated/rest-api-spec-update-main
branch
from
b7bdb35
to
182c797
Compare
github-actions
bot
force-pushed
the
automated/rest-api-spec-update-main
branch
5 times, most recently
from
ce56dba
to
b9b56de
Compare
github-actions
bot
force-pushed
the
automated/rest-api-spec-update-main
branch
3 times, most recently
from
b298565
to
9fc89b2
Compare
github-actions
bot
force-pushed
the
automated/rest-api-spec-update-main
branch
2 times, most recently
from
4dab274
to
ba87630
Compare
github-actions
bot
force-pushed
the
automated/rest-api-spec-update-main
branch
3 times, most recently
from
2fb72ea
to
a696c78
Compare
github-actions
bot
force-pushed
the
automated/rest-api-spec-update-main
branch
from
a696c78
to
d18df5a
Compare
As titled.