Hi @Anonymous ,
As per my research and discussion with internal teams, here are few workarounds you could try to overcome the limitations discussed in our previous comments:
- Instead of passing the actual data from the Lookup into the notebook you could try passing the query used in the Lookup to the notebook and have the notebook read from the SQL DB.
- Otherwise, you could stage that data in a parquet file and pass the location string into the notebook as well.
- The third option is to use Mapping data flows instead of Databricks if it fits your transformation logic.
Hope this info helps.
----------
- Please
accept an answer
if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how. - Want a reminder to come back and check responses? Here is how to subscribe to a notification.