Since Sunday (13-11-2023) I have been getting this error message on data imported through DataFlows. Previously they have been working. Has anyone else experienced this issue? SparkRuntimeException: Error while decoding: java.lang.IllegalArgumentException: requirement failed: Mismatched minReaderVersion and readerFeatures. newInstance(class scala.Tuple3). The Data Flows are linking to an on prem sql server database and I'm able to query the table in the sql endpoint, but cannot read the table into a dataframe. I've tried restricting the data to a couple of lines to see if there is unusual item in any of the queries, but nothing obvious and they previously worked. To get round this I've had to extract the data into csv files (using a python script in vs code) and then uploading the csvs to Files folders and then importing those files into a new table, which can be read using pyspark. I've had a couple of issues with Data Flows over the last week which makes me wonder how reliable they are.

Has there been a resolution to this issue? We are doing a POC w/ Fabric... and following Microsoft's own instructions we are getting this error. Doing the most basic of use cases... using a one step ADF pipeline w/ a Copy task to load an example dataset (NYC Taxi) into the lakehouse (no on-premises complications, no data gateways, etc.). Then attempting to access that table in a Notebook... fails w/ this same error. Error:SparkRuntimeException: Error while decoding: java.lang.IllegalArgumentException: requirement failed: Mismatched minReaderVersion and readerFeatures. newInstance(class scala.Tuple3) Delta log appears fine:{"protocol":{"minReaderVersion":1,"minWriterVersion":2}}

So, I found the root of the bug and also a temporary workaround. The bug is that Dataflows gen2 writes this in the json delta log files :{"protocol":{"minReaderVersion":1,"minWriterVersion":2,"readerFeatures":[],"writerFeatures":[]}} That's the reason for this error message : requirement failed: Mismatched minReaderVersion and readerFeatures A temporary fix is to change this string in all the _delta_log json files for the table to:{"protocol":{"minReaderVersion":1,"minWriterVersion":2}}You can change the log files within the onelake in your files browser:

Thanks very much... I suppose that Microsoft is working on this.. it doesn't make sense every day doing this process (if the DF runs each day)

Hi m_cherriman Thanks for using the Microsoft Fabric Community. Apologies for the inconvenience that you are facing here. At this time, we are reaching out to the internal team to get some help on this.We will update you once we hear back from them. Appreciate your patience. Thanks

Any news on this issue? We're experiencing the same problem. This is a real show stopper.

Error using data imported through DataFlow when using pyspark

26 Replies

KA78
Advocate I
2 years ago
So, I found the root of the bug and also a temporary workaround.

The bug is that Dataflows gen2 writes this in the json delta log files :
{"protocol":{"minReaderVersion":1,"minWriterVersion":2,"readerFeatures":[],"writerFeatures":[]}}
That's the reason for this error message : requirement failed: Mismatched minReaderVersion and readerFeatures

A temporary fix is to change this string in all the _delta_log json files for the table to:
{"protocol":{"minReaderVersion":1,"minWriterVersion":2}}
You can change the log files within the onelake in your files browser:
- jcvega
  Frequent Visitor
  2 years ago
  Thansk for the workarround.. I had the same issue.. How can I edit these files?
  - KA78
    Advocate I
    2 years ago
    You can change the files with the Onelake plugin that you can install in your windows file explorer :https://www.microsoft.com/en-us/download/details.aspx?id=105222
    
    Keep in mind that every time you execute the dataflow, you'll have to modify the new log file that has been created for this workaround. Hopefully they'll quickly fix this bug.
v-cboorla-msft
Microsoft Employee
2 years ago
Hi m_cherriman

Thanks for using the Microsoft Fabric Community.

Apologies for the inconvenience that you are facing here.

At this time, we are reaching out to the internal team to get some help on this.
We will update you once we hear back from them.

Appreciate your patience.

Thanks
- jeremycolson1
  Advocate I
  2 years ago
  Has there been a resolution to this issue? We are doing a POC w/ Fabric... and following Microsoft's own instructions we are getting this error. Doing the most basic of use cases... using a one step ADF pipeline w/ a Copy task to load an example dataset (NYC Taxi) into the lakehouse (no on-premises complications, no data gateways, etc.). Then attempting to access that table in a Notebook... fails w/ this same error.
  
  Error:
  SparkRuntimeException:
  Error while decoding: java.lang.IllegalArgumentException: requirement failed:
  Mismatched minReaderVersion and readerFeatures. newInstance(class scala.Tuple3)
  
  Delta log appears fine:
  {"protocol":{"minReaderVersion":1,"minWriterVersion":2}}
  - Reidy
    Regular Visitor
    2 years ago
    Hey,
    
    We got around this by downgrading the spark version in the environment used for our Notebooks. 1.1 works fine, 1.2 has the issue.
- v-cboorla-msft
  Microsoft Employee
  2 years ago
  Hi m_cherriman
  
  Thanks for using Fabric Community.
  Apologies for the issue you have been facing.
  
  Please go ahead and raise a support ticket to reach our support team:
  
  https://support.fabric.microsoft.com/support
  
  After creating a Support ticket please provide the ticket number as it would help us to track for more information.
  
  Thank you.
  - souldish
    Frequent Visitor
    2 years ago
    We are experiencing same issue with csv data coming from dataflow gen 2
KA78
Advocate I
2 years ago
Any news on this issue? We're experiencing the same problem. This is a real show stopper.
KA78
Advocate I
2 years ago
Hi,

v-cboorla-msft is there perhaps an update you can give us on this issue?
Also, if anyone should have a workaround, we would aprecieate it greatly. This is a real showstopper now.

Our ERP data resides in an on premise database that we can only access with ODBC. So the only way to get this data into Fabric (when using only fabric - we want to stay with SaaS) is by using Dataflow gen2. And now the tables created by Dataflow gen2, can't be used in a notebook. So we can't use a notebook / pyspark to tranform our data...

Does anyone know of a workaround, inside Fabric, so that we can combine ODBC on prem data + notebooks? Any help is greatly appreciated.

m_cherriman , did you perhaps find a solution?

Thanks in advance for any update or insight into this issue.
- v-cboorla-msft
  Microsoft Employee
  2 years ago
  Hi KA78
  
  Thanks for using Fabric Community and posting your question.
  
  Can you please create a new post as the initial ask is different from your issue? We will definitely look into the issue and help.
  
  Thanks for understanding.
  - KA78
    Advocate I
    2 years ago
    Thanks @v-cboorla-msft for your reply. I'll create a new post for my question regarding the workaround.
    
    Although, the root of the problem is the same as the initial ask. Is there perhaps something you can share about the status of the inital ask : "Error using data imported through DataFlow when using pyspark". Is this a known issue?
    
    (related to this error : "SparkRuntimeException: Error while decoding: java.lang.IllegalArgumentException: requirement failed: Mismatched minReaderVersion and readerFeatures. newInstance(class scala.Tuple3)." )
KA78
Advocate I
2 years ago
UPDATE:

I also created a ticket for this bug. I just received an email from support telling me it will be fixed this week ! 😀

"Would like to inform you that I have received an update from engineering team. The update says it was a dataflow bug whose fix will be done and rolled out to production by the end of this week.
For Dataflows Gen2, the fix should reach all production regions by the end of this week."

Thanks Microsoft for the great support!

It would be nice if we could see this kind of major issue in the known issues list in the future : Microsoft Fabric Known Issues
- KA78
  Advocate I
  2 years ago
  jcvega I'm just tagging you here so you'll get a notice that you don't have to put effort in the workaround. Should be fixed this week.
naanii
Frequent Visitor
2 years ago
Hello,

I am still experiencing the same issue.
Any update about this case?
- KA78
  Advocate I
  2 years ago
  Hi naanii, You'll also have to update your power bi gateway.
  - naanii
    Frequent Visitor
    2 years ago
    Thanks for the solution!
- Anonymous
  Not applicable
  2 years ago
  If you are using the gateway, make sure that you are using the latest version. The Dataflows Gen2 has been updated in all regions by 2/23. Let me know if that works.
souldish
Frequent Visitor
2 years ago
Still seeing issues with this....not connected to gateway and using DFG2 to connect to REST API and copy the data to a table in the lakehouse.

Any updates on this issue? it makes DFG2 completely unusable.
- souldish
  Frequent Visitor
  2 years ago
  I think i got the issue resolved. I'm not sure what exactly fixed it, but I removed a previous connection to an on prem gateway in my DFG2 even though the current flow wasn't using a gateway at all. Then, I re created the dataflow in a new DFG2. Something about the connection to the gateway was still being written to the files even though I wasn't using the on prem gateway connection. Weird.