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
Some options act on properties that can also be set with -D key=value, and there is no logic in place to prevent conflicts between the two settings. Together with the fact that we are still mirroring options between their Hadoop 1 and Hadoop 2 versions (see #274), this makes the actual setting dependent on dictionary iteration order in:
props= [(ctable.get(k, k), v) for (k, v) inself.properties.items()]
In particular, I saw one test pass with Python 3 and fail with Python 2 due to this.
The text was updated successfully, but these errors were encountered:
Some options act on properties that can also be set with
-D key=value
, and there is no logic in place to prevent conflicts between the two settings. Together with the fact that we are still mirroring options between their Hadoop 1 and Hadoop 2 versions (see #274), this makes the actual setting dependent on dictionary iteration order in:In particular, I saw one test pass with Python 3 and fail with Python 2 due to this.
The text was updated successfully, but these errors were encountered: