Skip to main content
Solved

OneLake source

  • 2 July 2024
  • 4 replies
  • 45 views

Hello,

TimeXtender: 20.10.31.64
ODX:  20.10.31

We have a case where a customer has to move from SQL database to a OneLake Parquet as the data extraction from one of their systems. We need to find a way to get this data into TimeXtender.

I could find that there is the possibility for one lake parquet connector, but it seems tied to the new version of TX as I can’t find that connector in our version of tx/odx.
 


Is there any possibility for us to do it another way while on our version? 

Thank you,
Victor
 

4 replies

daniel
Rank
Userlevel 4
Badge +6

Dear @Victor ,

As far as I know there is no OneLake connector in te Classic version.

What you could do or try is connect TX to the SQL endpoints in Fabric / the OneLake or kopie / convert the Delta parquets to tables in Fabric and connect to them (through the SQL endpoints).

Hope this helps

= Daniel

 

Thomas Lind
Rank
Userlevel 6
Badge +5

Hi @Victor 

If the data is going to be stored in parquet files there also exists a CData parquet provider.

I am not sure it is a better option than what suggested above, but it should also be able to connect to the data.

V
Rank
Userlevel 1

Thank you, will give these a try in the coming weeks.

rory.smith
Rank
Userlevel 6
Badge +7

Hi,

I don't think the CData parquet connector supports parquet stored in OneLake, but only ADLS. As far as I know the interfaces for OneLake are different, so I would not expect it to work.

Reply


Terms and ConditionsCookie settings