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.

Sign up for GitHub

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

Jump to bottom

usage of elasticsearch-api #3951

Open

jsnoble opened this issue Feb 5, 2025 · 1 comment

Labels

Member

jsnoble commented Feb 5, 2025 •

edited

Loading

Currently used apis:

validateGeoParameters
bulkSend
count
search
getEsVersion (this should be solved with client metadata)
version
isElasticsearch6
isAvailable
get
mget
index
indexWithId
create
update
remove
indexExists
indexCreate
indexRefresh
putTemplate
verifyClient

Types:

BulkRecord
Client
BulkActionMetadata

Used in:

Teraslice stores
elasticsearch assets and any reader/slicer/sender client from elasticsearch-asset-apis
Spaces (for sender and sliced fetching)
ESCachedStateStorage
Any operation using the apis provided and saved in teraslice for elasticsearch fetching/sending

Duplicate Test helpers are spread across the code

NO use of returning Dataframes from elasticsearch-api, only DataEntities

jsnoble added the documentation label

Member Author

jsnoble commented Feb 10, 2025

Elasticsearch-store usage:

Used In:

teraslice for tests helpers
terafoundation raw client creation
elasticsearch-assets: for testhelpers, raw client creation, client type, client metadata helpers (isOpensearch2 fn etc)
spaces mainly for types,
spaces-apis-utils for creating clients,
curator/deployer Index-manager
main use case in spaces-metadata-manager

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment