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/ add Elasticsearch database alternative for typesense #599

Merged
merged 223 commits into from
Oct 16, 2024

Conversation

bogdanfazakas
Copy link
Member

@bogdanfazakas bogdanfazakas commented Aug 11, 2024

Fixes #590 .

Changes proposed in this PR:

  • create abstract base database classes
  • created factory to instantiate one of the available databases
  • add elastic implementation for typesense databases
  • add datatoken address, nftAddress, did in order index or schemas

@bogdanfazakas bogdanfazakas self-assigned this Aug 14, 2024
@alexcos20 alexcos20 changed the base branch from develop to main August 14, 2024 18:59
Copy link
Member

@jamiehewitt15 jamiehewitt15 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me

@bogdanfazakas bogdanfazakas merged commit 821b8da into main Oct 16, 2024
12 checks passed
@bogdanfazakas bogdanfazakas deleted the feature/add-elasticdb branch October 16, 2024 09:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Database: Move from typesense to ElasticSearch
4 participants