You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I create a sub-partition, the order of the partition keys are different across Scala version 2.12 and 2.13, as they get combined with the parent partition's keys. This is probably because of a different behaviour in the ++ operator of ListMap.
It's not exactly clear to me, if this is a bug, or if the ordering of the partition keys is not relevant.
To Reproduce
Steps to reproduce the behavior OR commands run:
Using AtumAgent v0.2.0, execute the following commands:
Describe the bug
When I create a sub-partition, the order of the partition keys are different across Scala version 2.12 and 2.13, as they get combined with the parent partition's keys. This is probably because of a different behaviour in the
++
operator ofListMap
.It's not exactly clear to me, if this is a bug, or if the ordering of the partition keys is not relevant.
To Reproduce
Steps to reproduce the behavior OR commands run:
Using AtumAgent v0.2.0, execute the following commands:
In Scala 2.12
publishCtx.atumPartitions
isHowever, in Scala 2.13, it is
The issue seems to be a different behaviour of the
++
operator in ListMap between Scala 2.12 and 2.13.A similar example is the following code:
When executed in Scala 2.12.19, the output is
However, in 2.13.14, it is
Expected behavior
The order should be the same across Scala 2.12 and 2.13 (unless ordering in partition keys is not relevant anymore)
The text was updated successfully, but these errors were encountered: