gudehuang opened a new issue, #2010:
URL: https://github.com/apache/incubator-hugegraph/issues/2010

   ### Bug Type (问题类型)
   
   _No response_
   
   ### Before submit
   
   - [X] 我已经确认现有的 [Issues](https://github.com/hugegraph/hugegraph/issues) 与 
[FAQ](https://hugegraph.github.io/hugegraph-doc/guides/faq.html) 中没有相同 / 重复问题
   
   ### Environment (环境信息)
   
   - Server Version: v0.12.0
   - Backend: RocksDB x nodes, HDD or SSD 
   - OS: xx CPUs, xx G RAM, Centos 7.x 
   - Data Size: xx vertices, xx edges <!-- (like 1000W 点, 9000W 边) -->
   
   
   ### Expected & Actual behavior (期望与实际表现)
   
   期望:
   从0.10.4的数据迁移到0.12.0后,执行schema.vertexLabel('symptom').ifNotExist() 正常
   ```
   schema= graph.schema()
   schema.vertexLabel('symptom')
        .ifNotExist()
       .create();
   ```
   
   实际表现:
   在0.12.0上:
   
![image](https://user-images.githubusercontent.com/20537541/200490126-70ec517c-85c9-430d-99af-6324c8b70cbd.png)
   报错:The vertex label 'symptom' has existed
   
   在0.10.4上:
   正常
   
![image](https://user-images.githubusercontent.com/20537541/200490297-59f51c05-4698-498a-94b9-678d7bf7264c.png)
   
   
   
   
   
   ### Vertex/Edge example (问题点 / 边数据举例)
   
   _No response_
   
   ### Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构)
   
   ```javascript
   //数据如下
   
   schema = graph.schema()
   
   schema.propertyKey("createdAt").asDate().ifNotExist().create();
   schema.propertyKey("updatedAt").asDate().ifNotExist().create();
   
   
   schema.vertexLabel('symptom')
       .properties("createdAt", "updatedAt"
       )
       .nullableKeys("createdAt", "updatedAt"
       )
       .useCustomizeNumberId()
       .ifNotExist()
       .create();
   g.addV('symptom').property(T.id, 10010)
       .addV('symptom').property(T.id, 10011)
   ```
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to