Forum Discussion
Error with refresh through on-premise data gateway (Gen2 Dataflow) - "ParquetSharpNative"
Hi Anonymous , you are right, sorry. We have sent / uploaded the logs this morning via the open ticket #2402090050003022.
Further, we have downgraded the Gateway to September 2023 version and the Gen2 Dataflows work again! It seems also we are not the only ones having this issue since last week.
Thanks
- Timeout: I guess we've looked at this before right? This is from your Gen 1 vs Gen 2 dataflow comparison, where the Gen 1 DF was issuing Odata requests and getting an average of 0.5sec response time and Gen 2 was getting 3.5secs. This is from the S4 hana endpoint - is there any server logs to check why the response data rate is slower here? Note that both Gen1 and Gen2 refreshes are from the Germany data center.
- Gateway: This one is interesting, ParquetSharp should be bundled with the GW installer. I found the support case and will follow up internally.
- OAuth 2.0: if you reproduce this let me know. Sometimes the "invalid credentials" can be thrown due to firewall rules (some servers will deny your network access with a 401\403 even if you have the right creds)
I think given your scenarios, the best bet forward is to make your OnPrem Data Gateway work. There's perhaps some opportunities to tweak those OData queries to use the S4HANA connector, but just switching over to OPDG should resolve most of your issues. So let's focus on this one and I'll follow up on your support case to see how we can help with the ParquetSharp problem.
Yes, I agree that solving the Data Gateway problem would solve my situation. I can work around the timeout problem as this SAP endpoint is anyway responding very slow, maybe using a blob storage solution in Azure with a delta mechanism going forward. The memory allocation problem would also render irrelevant as I would anyway not want to mix Gen1 and Gen2 dataflows.
Thank you for your support. I hope we can fix the OPDG issue next week or so 🙂