You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Stephen Mallette (Jira)" <ji...@apache.org> on 2025/03/11 12:32:00 UTC
[jira] [Closed] (TINKERPOP-3104) Make unfold() on Maps consistent between embedded and remote use
[ https://issues.apache.org/jira/browse/TINKERPOP-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Mallette closed TINKERPOP-3104.
---------------------------------------
Resolution: Won't Do
While inconsistent, it doesn't seem like the value is high enough for the effort. Also, no clear solution that doesn't introduce more pain to GLVs unless embedded mode went to {{Map}} which doesn't feel right either.
Documented the differences and closing for now until it annoys again: https://github.com/apache/tinkerpop/commit/6dda6f0df96aa852d20cac40c48144786645a6b5
> Make unfold() on Maps consistent between embedded and remote use
> ----------------------------------------------------------------
>
> Key: TINKERPOP-3104
> URL: https://issues.apache.org/jira/browse/TINKERPOP-3104
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 4.0.0
> Reporter: Ken Hu
> Priority: Major
>
> The result of an unfolding a Map is different when run in embedded mode and when run remotely. In the embedded case, you'll get a Map.Entry, in the remote case, you'll get a size one Map. It would be better to make this consistent.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)