I've always had a big concern with this kind of behavior, because what
happens if the "new column" already exists but later in the header? It
seems like python/pandas deals with this by incrementing AGAIN, so they
read the header and THEN decide what to do with the values for duplicates
(make sense
The other option would be to migrate to the new fork of jsch -
https://github.com/mwiede/jsch, there's a few issues with connection
algorithms, etc but there's now at least support to add algorithms to the
list of existing ones in 3 ways (though not sure how VFS might support this
currently).
Davi
I had just started to look into this and was going to call out the same
thing. I'm concerned with those changes, especially the ones regarding the
allowDuplicates change, I made a note in my ticket for work to make sure we
have appropriate test cases on our end, with the RC, we didn't see any
issu
There's a few fixes in commons-csv 1.10.0, especially dealing with String
Delimiter fixes that we could really use in a released version, is there a
plan to release this soon?
Happy to help where I can to get it released, if that's needed.
David
