This has something to do with the changes made by issue 9352.  Prior to 9352 fix, either CR or LF is treated as a record separator; the change made by 9352 only accepts LF as a record separator. Hence, in the current ADS implementation, if a CSV file uses CR as the record separator, then the entire file is read in as a single record; if the 'First row contains column names' field is checked, then nothing will be displayed in the 'Sample File Columns' panel; if the 'First row contains column names' is unchecked, the one record is displayed in the 'Sample File Columns' panel.

@funfun: we need to change the behavior to do the following:

- If user has chosen Windows style line endings (CR/LF):

• if line contains CRLF, treat that as a single line ending (works in v14)
• if line contains LF only, treat that as a single line ending (works in v14)
• if line contains CR only, treat that as a single line ending (does not work in v14)

- If user has chosen Linux style line endings (LF):

• if line contains CRLF, treat the CR as a character that is part of the document and LF as a line ending (works in v14)
• if line contains CR only, treat that as a single line ending (does not work in v14)
• if line contains LF only, treat that as a single line ending (works in v14)

The above should match how v13 behaves

I've attached an additional file that has mixed CR and CRLF in the same csv

for illustrative purposes I've added screenshots showing:

a cr only file side by side of v13 and v14 - unix style eol setting
a cr and crlf mixed file side by side of v13 and v14 - unix style eol setting
a cr and crlf mixed file side by side of v13 and v14 - windows style eol setting
an image indicating the file with mixed CR and CRLF eol

Fixed - either CR or LF can be used as a record separator
   14.0  - SVN r34377/14.0.0-2
   trunk - SVN r34380/15.0.0-dev-23

Notes:
(1) v14 CSV filing parsing should behave the same way as v13 does, i.e., either CR or LF can be used as a record separator.
(2) In ADS, platform EOF specified in the Import dialog is not passed down to the low level object that is responsible for CSV file parsing.
(3) Also re-tested issue 9352 to ensure blanks are skipped. Now, 2 consecutive CRs also imply a blank line because CR is interpreted as a record separator.  Please retest 9352 in your environment, too.