graph-database

Description

Introduction

Minimal reproduce:

(root@nebula) [basketballplayer]> YIELD "player100" AS foo | FETCH PROP ON * $-.foo YIELD vertex as v,
+----------------------------------------------------+
| v                                                  |
+--------------------------------------------

Currently, ManagementSystem::printIndexes does not show the mappings for mixed indexes. Similar to JanusGraph/janusgraph#3126, we should include the same information in the output of printIndexes.

Problem Type (问题类型)

configs (配置项 / 文档相关)

Before submit

• 我已经确认现有的 Issues 与 FAQ 中没有相同 / 重复问题

Environment (环境信息)

• Server Version: v0.12.x
• Backend: RocksDB x nodes, HDD or SSD
• OS: xx CPUs, xx G RAM, Centos 7.x
• Data Size: xx vertices, xx edges <!-- (

See #1029

• existence_error for an unknown flag
• syntax_error('disallowed: <shortflag>=<value>') when passing -c=true (terminusdb/terminusdb#1216)

It appears that all the dependencies required by Gaffer are available in Maven central, which is the default repository used by Maven. Although this may not have been the case in the past. When running builds Maven occasionally tries to check repos.spark-packages.org if it can't find a package in Maven central. This is often because of a mistake with the version.

It's unclear if this reposito

Describe the bug
The strings for the Topics values in the UI does not appear to be translated.

To Reproduce
Steps to reproduce the behavior:

1. Go to any dataset or investigation:
2. Create an entity - Person or Company
3. Add a topic property to the entity
4. Go to the dataset search page
5. Filter by Topics and you'll see that the values are not translated.

**Expected behavi

Feature description (Mandatory)

Please add the capability to specify the type of array instead of defaulting to string. i.e.
apoc.array.int()

How this feature can improve the project?

By default, it is created as a string. Some customers have asked for the ability to hint at the data type.

This enable more portability on Linux platform.

If you do object.association.distinct.other_association, the distinct goes away.

This is probably good for the simple implementation, but we could have a WITH DISTINCT automatically go in there on the second association