-
Notifications
You must be signed in to change notification settings - Fork 525
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] HugeGraph could not process Inifnity/NaN value in float/double #1575
Comments
u define a pk or u can paste the phrase like |
Thanks for your advice. Double.Infinity value means an infinite value of type Double. It is a special constant which is equal to the value returned by Double.longBitsToDouble (0x7ff0000000000000L). When the divisor is equal to 0, the result returns the Double.Infinity value. In our case, new Double(1029.98 / 0) is the Double.Infinity value. We can do this in both JanusGraph and Neo4j-Gremlin but not in HugeGraph. That’s why we think HugeGraph could not process Double.Inifnity value. |
Get it, the reason is we skip Another question: after the support, u'll get a price value "Infinity"(string) in json, seems u need also handle it in upper logic? |
@zhengyingying, hi, I submit a PR for this issues, u can cherry-pick it or copy the DataType code directly, then test in client & your cases to check if it's suitable. Hope to get your reply & suggestion. THX |
@imbajin Thanks for your reply. We will test it in our cases. |
Any response for the linked PR? (Need to ensure it's suitable for user to use) Wait for your test result, THX ~ ⏲️ |
Due to long time with no response, we merge the linked pr first. Looking forward to your follow-up feedback on this issue (and reopen it if need) |
Bug Type (问题类型)
gremlin (结果不合预期)
Before submit
Environment (环境信息)
Expected & Actual behavior (期望与实际表现)
Expected Behavior
We expected to write
Double.Infinity
value into HugeGraph.Current Behavior
An exception was thrown.
Steps to Reproduce
Vertex/Edge example (问题点 / 边数据举例)
No response
Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构)
No response
The text was updated successfully, but these errors were encountered: