-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support of setting the arangoDB name on the configuration #772
Comments
No, this isn't possible. The database is an internal part of the system and is not something you can easily select on a request basis. My recommendation for your use-case would be to simply augment your execution plan and event objects with the DBR cluster name stored as an extra parameter, or a tag, and filter the stuff on the UI based on that (the feature beta is available in the develop version of the server and the UI). Alternatively, you may augment the URIs for the input/output sources to include the cluster name as a part of the name. That is another way to logically separate the lineage data. If you absolutely want to use different DBs then you can run separate Spline instances, put a custom proxy gateway in front of the Spline Producer REST API (or implement a custom |
About Do you mean that the name of the cluster is on the execution plan? |
Does the feature Beta is available as a maven in the Databricks? |
No. You need to build and install from the laters development branch. |
Any chance that it will be on the cloud of Databricks soon? |
no ETA unfortunately. The team has no capacity and the business priorities changed. So the project is on hold at the moment. |
Hi |
Hi
I am using spline to capture lineage from Databricks notebooks
I put on the cluseter - on the advanced settings
since i have several customers- i dont want to keep the data of all of them on the same arangoDB
so I want a way that the response will be kept on a db per customer.
can we send also the arangoDb name as a parameter so the execution plan lineage data will be kept on a different db
for each cluster i use
thanks in advance
The text was updated successfully, but these errors were encountered: