Skip to content

[C++][Dataset] Ensure that dataset code is robust to schemas with duplicate field names #23685

Closed

Description

@asfimport

Fields in a schema don't have to have unique names, so we should make sure we're not assuming that.

Reporter: Neal Richardson / @nealrichardson
Assignee: Ben Kietzman / @bkietz

Related issues:

PRs and other links:

Note: This issue was originally created as ARROW-7412. Please see the migration documentation for further details.

Activity

  1. asfimport commented on Jan 6, 2020

    @asfimport
    Author

    Ben Kietzman / @bkietz:
    For now, we should probably just error if a field is referenced whose name is not unique.

  2. asfimport commented on Feb 18, 2020

    @asfimport
    Author

    Ben Kietzman / @bkietz:
    A more general solution would be provide an unambiguous way to refer to fields https://docs.google.com/document/d/1-aoAb1d00BfCcEP--kmYWDBb_eeOFgtlSVPPjSGy8ko/edit

  3. asfimport commented on Mar 13, 2020

    @asfimport
    Author

    Ben Kietzman / @bkietz:
    Issue resolved by pull request 6545
    #6545

  4. added this to the 0.17.0 milestone on Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions