[PIG-998] revisit frontend logic and pig-latin semantics

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.9.0
• Assignee: Daniel Dai
• Reporter: Thejas Nair
• Created: 07/Oct/09 19:36
• Updated: 04/Aug/11 00:34
• Resolved: 15/Mar/11 01:50

Description

This jira has been created to keep track of issues with current frontend logic and pig-latin semantics.
One example is handling of type information of map-values. At time of query plan generation pig does not know the type for map-values and assumes it is bytearray. This leads to problems when the loader returns map-value of other types.

Issue Links

• is blocked by: PIG-1065 In-determinate behaviour of Union when there are 2 non-matching schema's
• is blocked by: PIG-847 Setting twoLevelAccessRequired field in a bag schema should not be required to access fields in the tuples of the bag
• is related to: PIG-1112 FLATTEN eliminates the alias

Sub-Tasks

• sorting on map-value fails if map-value is not of bytearray type: Closed
• Pig get confused if map value is not bytearray: Closed