[Feature] OPEAStore: OPEA data store framework

[joshuayao]

Priority

P2-High

OS type

Other (Please let us know in description)

Hardware type

Xeon-GNR

Running nodes

Other

Description

For traditional databases, OPEA requires a data store framework that enables contributors to integrate new databases seamlessly. This includes but not limits to abstract the data store and consolidate the access interface.

• feature: OpeaStore Class #1493

The owner is @aMahanna

[rbrugaro]

@joshuayao the OpeaStore abstraction enables 1)single API for any database vendor integration 2) abstraction for the data type. Currently in the repo feedback management, chat history and prompt registry microservices are same code just differing in input data. With OpeaStore we can now deprecate these 3 independent microservices and refactor any examples that made use of that to leverage the OpeaStore instead. Please create a separate issue to track that.

Also, the DatapreRequests you linked here is unrelated. It's needed for Arango dataprep and retriever integration
cc @aMahanna

[joshuayao]

@joshuayao the OpeaStore abstraction enables 1)single API for any database vendor integration 2) abstraction for the data type. Currently in the repo feedback management, chat history and prompt registry microservices are same code just differing in input data. With OpeaStore we can now deprecate these 3 independent microservices and refactor any examples that made use of that to leverage the OpeaStore instead. Please create a separate issue to track that.

Also, the DatapreRequests you linked here is unrelated. It's needed for Arango dataprep and retriever integration cc @aMahanna

Hi @rbrugaro Thanks for your updates.