big-ocean-9800
05/04/2023, 6:15 PMv0.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:
```
-[ 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.lively-cat-88289
05/04/2023, 6:16 PMastonishing-answer-96712
05/05/2023, 5:45 PMaloof-gpu-11378
05/10/2023, 9:13 PM