Closed srstsavage closed 1 year ago
Until fixed, a workaround is to append a JEXL comment with a unique value after the duplicate fixed value, e.g.
<sourceName>=5.0##1234unique</sourceName>
...
<sourceName>=5.0##5678unique</sourceName>
I will fix this.
Another similar (and nicer looking) workaround is to append a different number of 0's after each sourceName =5.0 =5.00 =5.000
I will not be making this change. It turns out that the sourceNames, including =expression sourceNames, really do need to be unique. It has to do with the part of the code that selects the columns that are needed in the source file to fulfill the user's request. Each sourceName has to uniquely link to a specific destinationName. So the long term solution will have to be the workaround that I suggested above (or something similar).
Fixed Value sourceNames are not excluded from duplicate column name detection. A dataset containing multiple columns with the same fixed value sourceName, e.g.
will result in a
com.cohort.util.SimpleException: ERROR: Invalid Table: Duplicate column names
error, e.g.Seems like any fixed or calculated
sourceName
(starting with=
) should be excluded from duplicate detection.