[jira] [Updated] (METAMODEL-100) AbstracColumn.equals(..) does not take into account the column number

["Kasper Sørensen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/METAMODEL-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kasper Sørensen updated METAMODEL-100:
--------------------------------------
    Fix Version/s: 4.4.0

> AbstracColumn.equals(..) does not take into account the column number
> ---------------------------------------------------------------------
>
>                 Key: METAMODEL-100
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-100
>             Project: Apache MetaModel
>          Issue Type: Bug
>    Affects Versions: 4.3.0-incubating
>            Reporter: Kasper Sørensen
>            Assignee: Kasper Sørensen
>             Fix For: 4.4.0
>
>
> I ran into a rare issue the other day: While reading a CSV file that had duplicate column names, doing a subselection on the table caused the values at the position of the duplicated column names to be duplicated values instead of the values really at the records.
> The table layout would be like:
> {code}
> foo,foo,bar
> 1,2,3
> 4,5,6
> {code}
> But while selecting "foo", "foo" and "bar" it emitted records:
> {code}
> 1,1,3
> 4,4,6
> {code}
> After some debugging it seems that the indexOf(...) calls on the DataSetHeader is eventually delegating to an equals(..) call on AbstractColumn. This equals method does not take into account the column number and thus the columns are deemed equal although they are not.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)