This issue is now recognized as a bug in Mathematica 11.2.

See the below link:

Bug Introduced In Mathematica 11.2

Hi Alexey,

I'm sort of at a loss at what more we can do.

As pointed out in a number of posts, there are things that a user can do to minimize the impact of importing/exporting data between releases of Mathematica. But all that responsibility falls on the user.

But I think Wolfram Technical Support does not fully understand how such a small issue of importing data incorrectly can lead to all sorts of mysterious user application problems. If you data is inconsistent, your results are going to be inconsistent. Data integrity is a basic requirement. This huge. All other issues of new functionality and features are secondary.

Take a simple example of storm outages from the last hurricane in Florida. Suppose you upgrade to Mathematica 11.2 to take advantage of new features and functionality of dealing with huge amounts of storm data. And a lot of your data is stored in temporary CSV file extracts. And then unknown to you, CSV imports of customers outage data, truncate or drops rows of customer outage data. So in your post processing, it looks like you've made great progress in power restoration, when customers are still reporting little or no progress.

Importing/Exporting data consistently is something everyone assumes every product does, correctly 100% of the time. When this showed up after a few days of the general release of Mathematica 11.2, they should of fixed it immediately. The fact that it is still not fixed, well ... Leaving it to the Mathematica user community to encounter a problem, and then search Mathematica support blogs for help, is like a car company leaving it to the dealers to fix know problems with their new cars. It works, but it makes everyone unhappy.

Still hoping that Wolfram will act, but I haven't heard anything from them since my last two emails on the broader issue of data integrity.

Hi again Marco! Now this statement looks interesting. I will have to try it! The thing is, I still want that conversation with Wolfram technical support. Without that "TextDelimiters"->"" parameter, CSV file Imports under Mathematica 11.2 are loosing/truncating data. Without anyone being aware of it. That should never, never happen. Even if there is a parameter fix, like "TextDelimiters"->"" available, it should not be left to the hundreds of thousands of users of Mathematica, to discover the problem, and fix every CSV Import statement across every program they have. No, this needs to be fixed by Wolfram ASAP, before many, many users run into the same issue. And while they are at it, Wolfram should also fix the Import elapsed time problem, again, not leaving it to their user base to modify all their CSV Import code. I've done my part and opened a problem record on this with Wolfram. Waiting for their call.... Best Regards!!!

Hi, I' m on 11.2 with Windows 10. When I Import the file (standard Import) the data seems ragged. One column was missing data here and there. Import went fast (0.5 sec). I opened the file with Excel and saw some "strange" field like carbon‐oxygen white dwarf I saved the file in MSDOS CSV and reimported. Now the file seemed to read in: Still don't know if it's like expected.