[RFC] Intel-ArangoDB joint RFC for txt2query microservice abstraction with vendor integrations#387
[RFC] Intel-ArangoDB joint RFC for txt2query microservice abstraction with vendor integrations#387rbrugaro wants to merge 1 commit intoopea-project:mainfrom
Conversation
rbrugaro
requested review from
chensuyue,
chickenrae,
ftian1,
mkbhanda and
preethivenkatesh
as code owners
|
@jeanyu-habana could you please review this RFC and specifically comment on the txt2cypher gaudi files within the txt2cypher microservice folder? Thanks! |
Signed-off-by: rbrugaro <rita.brugarolas.brufau@intel.com>
| @@ -0,0 +1,101 @@ | |||
| # Intriduce "txt2query" microservice with vendor integration to replace individual txt2cypher, txt2sql microservices | |||
|
|
|||
| Txt2query is a microservice abstraction for all different query languages. It follows same design philosophy as current dataprep, retriever and OPEAStore microservices. | |||
There was a problem hiding this comment.
the design looks good! but the folder name Txt2query doesn't make sense. the name txt2query has nothing to do with the functions of txt2sql or txt2cypher and can be confusing.
There was a problem hiding this comment.
What about txt2ql? ql would represent query language
natural-language-service is also another option
There was a problem hiding this comment.
other options: txt2dbql ( txt 2 data base query language), txt2DBquery , nl2ql (natural language 2 query language)
|
This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
|
This PR was closed because it has been stalled for 7 days with no activity. |
4 participants
This is a joint RFC between Intel and ArangoDB proposing a txt2query microservice abstraction following the same design approach of dataprep, retriever and OPEAStore.
cc: @aMahanna