Elastic Search for Cardinality List with meta-properties

未关闭
  • 哪里不对？
#4,221 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
elasticsearch, java
领域
databases, search

调研方向

首先查看提议的 Gremlin 查询、semi-code declareElasticsIndex 示例，以及链接的 Stack Overflow 和邮件列表讨论。定义 LIST cardinality 和可选元属性所需的行为，然后验证索引查询仅返回与请求的日期和创建者匹配的值。

由索引模型根据 Issue 内容生成。

描述

Elastic Search for Cardinality List with meta-properties:
The idea is to have Elastic Search index on the vertex property declared (optional) with schema Cardinality.LIST
and having these values on that list indexed also by their corresponding meta-data (optional).

Meta-data:
Meta-data is often used to retrieve only a "slice" of the data, but that is not well supported by the indexes, as all variations are returned, and that requires additional filtering. In case of our production that means a lot of processing in our temporal system.
Example:

g.V(1234).properties('name').valueMap()
==>[date:2014,creator:stephen]
==>[date:2015,creator:oleksandr]

we need to search only for string of "name" that were created in 2015, with Gremlin examples:
like:
g.V().hasLabel("My_VERTEX").has("name","abcabc").where(__.properties("name").has("date", P.gte, 2015).has("creator", P.eq, "oleksandr" ))
or like:
g.V().hasLabel("My_VERTEX").has("name","abcabc").has("name.date", P.gte, 2015).has("name.creator", P.eq, "oleksandr" )

by something like (semi-code):
declareElasticsIndex( "MY_VERTEX_BY_NAME", JanusGraphVertex.class, "MY_VERTEX", "name", "name.date", "name.creator" ) )

See also:
stackoverflow
lfaidata

主要语言
Java
星标
5.9k
派生
1.2k
平均合并
2 天 11 小时
30 天内合并 PR
67

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

JanusGraph/janusgraph 的其他 Issue

查看 JanusGraph/janusgraph 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。