Tableau Ingestion via Edge
Has anyone successfully ingested Tableau via Edge? In our case all Tableau assets come into a single BI Folder, instead of one BI Folder per Tableau Project like the job server does. It is unusable like this. Maybe we have something configured wrong?
jeffevoy
Posted 3 years ago · Edited 1 year ago·Last reply 2 years ago
13 comments
saamhooshmand
·2 years ago · EditedThanks for the quick reply! We tried the custom cert property, but maybe we provided an incorrect cert. Thanks for the help!
Saam
Kestutis_Daugela
·3 years ago · EditedOn the side note, maybe anyone found a workaround regarding self-signed certificates for tableau lineage harvester on edge? We have tableau server on-prem that is using custom cert. Standalone Lineage Harvester works fine (since it picks up cert from the server), but lineage harvester on edge would be ideal for scheduling and performance.
Typical handshake error, if it’s not k3s, would be easy to solve
harvester.error.ProcessingError: Unclassified Harvester error: 1 errors during loading sources: harvester.error.SourceProcessingError: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
p.s. Issue is registered and Collibra engineering is working on it.
Kestutis_Daugela
·3 years ago · EditedOn the side note, maybe anyone found a workaround regarding self-signed certificates for tableau lineage harvester on edge? We have tableau server on-prem that is using custom cert. Standalone Lineage Harvester works fine (since it picks up cert from the server), but lineage harvester on edge would be ideal for scheduling and performance.
Typical handshake error, if it’s not k3s, would be easy to solve
harvester.error.ProcessingError: Unclassified Harvester error: 1 errors during loading sources: harvester.error.SourceProcessingError: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
p.s. Issue is registered and Collibra engineering is working on it.
Venu Sura
·2 years ago · Edited@Kestutis_Daugela , I'm also getting the same error, Did you resolved the issue ? Thanks
Robert Lew
·2 years ago · Edited@Kestutis_Daugela Hi, we're getting this same error with Tableau lineage over Edge. Was there a resolution to this that you can please share?
Hock Khoo
·3 years ago · EditedWe’re in the process of testing this to go live. Raised an ideation that you can’t do filtering and assigning out target domains. It’s just going to make the assigning a lot more complex for us.
Found an issue in the operating model for Tableau assets: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/Tableau2.0/ref_tableau-operating-model.htm
For any domains that you filter/target to, there’s no Tableau Site that will allow for the hierarchy to work properly. We’ve developed a workaround that involved creating a dummy Tableau Site asset in each Domain and moving the relationship of Tableau Projects from the original Tableau Site to the new Tableau site.
Hock Khoo
·3 years ago · EditedWe’re in the process of testing this to go live. Raised an ideation that you can’t do filtering and assigning out target domains. It’s just going to make the assigning a lot more complex for us.
Found an issue in the operating model for Tableau assets: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/Tableau2.0/ref_tableau-operating-model.htm
For any domains that you filter/target to, there’s no Tableau Site that will allow for the hierarchy to work properly. We’ve developed a workaround that involved creating a dummy Tableau Site asset in each Domain and moving the relationship of Tableau Projects from the original Tableau Site to the new Tableau site.
jeffevoy
OP3 years ago · EditedHock: We’ve successfully ingested Tableau projects using domain mapping but are seeing exactly what you’re talking about here. The lineages just don’t work. I’m preparing to write a script to properly display them. Are you willing/able to share how you implemented your hack?
Regards,
Jeff Evoy
Hock Khoo
·3 years ago · EditedI ended up writing a workflow that in each Domain for Tableau Projects and Tableau Site asset types, we see what the parent asset (again just Tableau Site and Tableau Project) was with the assembles relationship. The child asset.
If the parent asset wasn’t in the same domain, I basically created a new asset (with attributes) and relationship to the new asset.
Then, for the parent asset, I did the same thing. But this time it’s the child. And I remembered the new child and the old child (basically, if the new and old child aren’t the same then it’s a new relationship).
I did this all in a function loop that created parents, which called the same create parent until the parent was in the same domain.
jeffevoy
OP3 years ago · EditedRosario:
Thanks for the quick reply and the very helpful tips. I’ll dig into this and let you know how it goes. .
jeffevoy
OP3 years ago · EditedRosario:
Thanks for the quick reply and the very helpful tips. I’ll dig into this and let you know how it goes. .
rosariocarbone
·3 years ago · EditedHi Jeff, I noticed I forgot the domain Id (as UUID) in the JSON example, however I recommend to follow the documentation, you also have an example in there.
rosariocarbone
·3 years ago · EditedHi Jeff, I haven’t done it but I need to do it soon.
For “BI Folder” do you mean “BI Catalog” domain?
My understanding is that if you want to ingest your Tableau projects assets into different BI Catalog domains in Collibra you need to use the configuration: https://productresources.collibra.com/docs/collibra/2023.01/Content/Catalog/Tableau2.0/Configuration/ta_prepare-source-id-configuration-file-for-tableau.htm
I think you need to use the “filters” + “projects” so that you can assign different domain IDs as target.
Something like this:
{
“filters”: {
“projects”: {
“tableausite” > “project1”: “”,
“tableausite” > “project2”: “”
}
}
}
In the documentation there is an example of this configuration though I noticed the format of the JSON file is slightly different.
The above is the JSON configuration where and are the UUIDs (unique identifiers) or your target BI Catalog domains in Collibra.
While for the Lineage Harvester this is a separate JSON file in your configuration when you use Edge (your case) for harvesting lineage from Tableau this JSON text should be created in the “Source Configuration” field of your “Tableau connection” configuration.
Regards
Rosario