Skip to content
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

[FEATURE] Move Opensearch Related functions out of the CORE layer. #930

Closed
vmmusings opened this issue Oct 19, 2022 · 1 comment
Closed
Labels
duplicate This issue or pull request already exists maintenance Improves code quality, but not the product

Comments

@vmmusings
Copy link
Member

Is your feature request related to a problem?
Currently Opensearch match functions are written in core layer and exposed to all kinds of catalogs. The ask from this issue to move these opensearch specific functions to opensearch connector and expose it via StorageEngine Interface.

What solution would you like?

What alternatives have you considered?
A clear and concise description of any alternative solutions or features you've considered.

Do you have any additional context?
Add any other context or screenshots about the feature request here.

@vmmusings vmmusings added enhancement New feature or request untriaged and removed untriaged labels Oct 19, 2022
@dai-chen dai-chen added maintenance Improves code quality, but not the product and removed enhancement New feature or request labels Oct 28, 2022
@dai-chen dai-chen added the duplicate This issue or pull request already exists label Dec 14, 2022
@dai-chen
Copy link
Collaborator

Duplicate as #811. Closing to track in one place. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists maintenance Improves code quality, but not the product
Projects
None yet
Development

No branches or pull requests

2 participants