SebastianGruza commented on PR #3209: URL: https://github.com/apache/hugegraph/pull/3209#issuecomment-5913199197
Round 4 in 0bb7724a: a property key's userdata is read exactly in the API and when the schema is read back from the backend (a DECIMAL `~default_value` keeps every digit across a restart, and is normalized to the key's type on every path, so a DOUBLE default stays a number), the `properties` filter of the list APIs is read exactly and normalized to the key's type, `IN`/`NOT_IN` compare by value once a BigDecimal is involved, in both `Condition` copies; docs in apache/hugegraph-doc#504. Tests: `PropertiesDeserializerTest` 3/3, `JsonUtilTest` 12/12, `ConditionTest` core 21/21 and struct 2/2, `VertexApiTest` from the api-test profile on rocksdb 6/6 and hstore 6/6 with the server and the three Stores built from this head (number-literal filter, DECIMAL default on create and on reading the key back), `DecimalPropertyApiTest` from #771 6/6 against this server. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
