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
The underlying cause is that StructuredDataOutputNode sets the key field to the fully qualified source field name (s1.k), while the actual schema uses the projected names (s1_k).
The text was updated successfully, but these errors were encountered:
rodesai
changed the title
stream-table join should preserve key column for result stream
join should preserve key column for result stream
Feb 21, 2019
Take the following series of statements:
The first join has no repartition:
The second one does:
The second join doesn't need to repartition though, since the key has not changed and is the join key.
Note that this can be avoided by an explicit
partition by
:The underlying cause is that StructuredDataOutputNode sets the key field to the fully qualified source field name (s1.k), while the actual schema uses the projected names (s1_k).
The text was updated successfully, but these errors were encountered: