[jira] [Updated] (ARROW-7173) [Integration] Add test to verify Map field names can be arbitrary
[ https://issues.apache.org/jira/browse/ARROW-7173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated ARROW-7173: -- Labels: pull-request-available (was: ) > [Integration] Add test to verify Map field names can be arbitrary > - > > Key: ARROW-7173 > URL: https://issues.apache.org/jira/browse/ARROW-7173 > Project: Apache Arrow > Issue Type: Test > Components: Integration >Reporter: Bryan Cutler >Assignee: Antoine Pitrou >Priority: Major > Labels: pull-request-available > Fix For: 1.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > A Map has child fields and the format spec only recommends that they be named > "entries", "key", and "value" but could be named anything. Currently, > integration tests for Map arrays verify the exchanged schema is equal, so the > child fields are always named the same. There should be tests that use > different names to verify implementations can accept this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARROW-7173) [Integration] Add test to verify Map field names can be arbitrary
[ https://issues.apache.org/jira/browse/ARROW-7173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Pitrou updated ARROW-7173: -- Priority: Major (was: Minor) > [Integration] Add test to verify Map field names can be arbitrary > - > > Key: ARROW-7173 > URL: https://issues.apache.org/jira/browse/ARROW-7173 > Project: Apache Arrow > Issue Type: Test > Components: Integration >Reporter: Bryan Cutler >Assignee: Antoine Pitrou >Priority: Major > Fix For: 1.0.0 > > > A Map has child fields and the format spec only recommends that they be named > "entries", "key", and "value" but could be named anything. Currently, > integration tests for Map arrays verify the exchanged schema is equal, so the > child fields are always named the same. There should be tests that use > different names to verify implementations can accept this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARROW-7173) [Integration] Add test to verify Map field names can be arbitrary
[ https://issues.apache.org/jira/browse/ARROW-7173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wes McKinney updated ARROW-7173: Fix Version/s: 1.0.0 > [Integration] Add test to verify Map field names can be arbitrary > - > > Key: ARROW-7173 > URL: https://issues.apache.org/jira/browse/ARROW-7173 > Project: Apache Arrow > Issue Type: Test > Components: Integration >Reporter: Bryan Cutler >Priority: Minor > Fix For: 1.0.0 > > > A Map has child fields and the format spec only recommends that they be named > "entries", "key", and "value" but could be named anything. Currently, > integration tests for Map arrays verify the exchanged schema is equal, so the > child fields are always named the same. There should be tests that use > different names to verify implementations can accept this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARROW-7173) [Integration] Add test to verify Map field names can be arbitrary
[ https://issues.apache.org/jira/browse/ARROW-7173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Pitrou updated ARROW-7173: -- Summary: [Integration] Add test to verify Map field names can be arbitrary (was: Add test to verify Map field names can be arbitrary) > [Integration] Add test to verify Map field names can be arbitrary > - > > Key: ARROW-7173 > URL: https://issues.apache.org/jira/browse/ARROW-7173 > Project: Apache Arrow > Issue Type: Test > Components: Integration >Reporter: Bryan Cutler >Priority: Minor > > A Map has child fields and the format spec only recommends that they be named > "entries", "key", and "value" but could be named anything. Currently, > integration tests for Map arrays verify the exchanged schema is equal, so the > child fields are always named the same. There should be tests that use > different names to verify implementations can accept this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
