Hey folks! My team created a custom ingestion sour...
# troubleshoot
b
Hey folks! My team created a custom ingestion source for CockroachDB (we are planning on contributing this change back to the community in the next couple of weeks). This Source is almost exactly the same as the Postgres Source . Here’s a link to the custom source in a GIST. This was working for us up until we upgraded from
v0.8.41
to
v0.9.5
. The main issue we are seeing is that browse paths are not working as expected. Before, the browse path was properly being populated based on instance name and database name, now it’s being truncated to just the platform name after we run an ingest. Here’s an example of two different versions of the
browsePaths
aspect for the same URN before and after the upgrade:
Copy code
```
-[ RECORD 1 ]--+--------------------------------------------------------------------------------------------------------------------------------------------------------
urn            | urn:li:dataset:(urn:li:dataPlatform:CockroachDB,test-instance.test-database.test-schema.test-table,PROD)
aspect         | browsePaths
version        | 0
metadata       | {"paths":["/prod/cockroachdb"]}
systemmetadata | {}
createdon      | 2023-01-05 17:35:19.596
createdby      | urn:li:corpuser:__datahub_system
createdfor     |
-[ RECORD 2 ]--+--------------------------------------------------------------------------------------------------------------------------------------------------------
urn            | urn:li:dataset:(urn:li:dataPlatform:CockroachDB,test-instance.test-database.test-schema.test-table,PROD)
aspect         | browsePaths
version        | 1
metadata       | {"paths":["/prod/cockroachdb/test-instance/test-database/test-schema/test-table"]}
systemmetadata | {}
createdon      | 2022-07-29 22:08:16.392
createdby      | urn:li:corpuser:__datahub_system
createdfor     |
```
Here you can see that the browse path is no longer being populated the same way, even though the ingestion source code has not changed. Does anyone know if we are missing something around this browsePaths issue? My understanding is that nothing should have changed around this after the version upgrade. I’ve been looking through the ingestion source code but haven’t found any smoking guns yet.
📖 1
🔍 1
l
Hey there 👋 I'm The DataHub Community Support bot. I'm here to help make sure the community can best support you with your request. Let's double check a few things first: ✅ There's a lot of good information on our docs site: www.datahubproject.io/docs, Have you searched there for a solution? ✅ button ✅ It's not uncommon that someone has run into your exact problem before in the community. Have you searched Slack for similar issues? ✅ button Did you find a solution to your issue? ❌ Sorry you weren't able to find a solution. I'm sending you some tips on info you can provide to help the community troubleshoot. Whenever you feel your issue is solved, please react ✅ to your original message to let us know!
a
@gray-shoe-75895 might be able to provide some guidance here
a
The second browse path actually looks more correct, although it shouldn’t include the final test-table piece. Is that causing issues for you?