Summarize conversation ```Customer: Customer A

Use case: Customer A has an ETL process to transform data on Databricks that involves several SQL steps and each of them creates temporary tables used by the next step:
Step 1 creates temporary table temp_A
Step 2 creates temporary table temp_b reading temp_a
Step 3 creates temporary table temp_c reading temp_b
etc
The temporary table won't be in our product.

Ask: since the temporary table won't be inX the standard miner won't be able to generate properly the lineage.
The customer would like to be able to invoke our SQL Parser as a web service to be able to get a dissected (parsed) version of the query back so that they can instrument it with object names (real tables and schemas) and then push the lineage to Company with API.
Is it something possible at all?

 NAME_1 from customer A told me that he has discussed the same with you
Yes, if we expose an API which we should, it unlocks a lot of use cases for other customers as well. Cc 
@NAME_2
 
@Amit NAME_3
 if we open up an rest API endpoint for our parser, lot of use cases open up.
NAME_2
  2 days ago
We exposed something similar in 1.0 as NAME_4 service : https://github.com/Companyhq/NAME_4
Tho it was not built scale first
Our Miners support this kind of temporary table lineage. Our current version of Databricks miner creates lineage using Databricks UC. But a S3 based solution where they dump the queries in a prefix can solve this use case.

Exposing an endpoint is also a solution but requires manual interventi Provide your reponse without using the word temp_c.
user