Question in `bootstrap_mce.json` regarding dataset...
# getting-started
w
Question in
bootstrap_mce.json
regarding datasets appearing under browse path "prod":
Copy code
"com.linkedin.pegasus2avro.metadata.snapshot.DatasetSnapshot": {
        "urn": "urn:li:dataset:(urn:li:dataPlatform:hive,SampleHiveDataset,PROD)",
        "aspects": [
          {
            "com.linkedin.pegasus2avro.common.Ownership": {
              "owners": [
                {
                  "owner": "urn:li:corpuser:jdoe",
                  "type": "DATAOWNER",
                  "source": null
                },
                {
                  "owner": "urn:li:corpuser:datahub",
                  "type": "DATAOWNER",
                  "source": null
                }
              ],
              "lastModified": {
                "time": 1581407189000,
                "actor": "urn:li:corpuser:jdoe",
                "impersonator": null
              }
            }
          },
          {
            "com.linkedin.pegasus2avro.dataset.UpstreamLineage": {
For the above mentioned Hive dataset, there is no mention of following type of
BrowsePaths
the ways Kafka and Hdfs DatasetSnapshot.
Copy code
"com.linkedin.pegasus2avro.common.BrowsePaths": {
              "paths": ["/prod/kafka/Sample..."]
            }
How is the path
/prod/hive/SampleHiveDataset
appearing on the UI ? OTOH, I see several ML snapshot mentioning browse paths, but those don't appear on the UI. e.g.
Copy code
"com.linkedin.pegasus2avro.metadata.snapshot.MLFeatureTableSnapshot": {
        "urn": "urn:li:mlFeatureTable:(urn:li:dataPlatform:feast,test_feature_table_no_labels)",
        "aspects": [
          {
            "com.linkedin.pegasus2avro.common.BrowsePaths": {
              "paths": ["/feast/test_feature_table_no_labels"]
            }
          },
What is the criteria on which some are displayed under browse paths on the UI?
g
Hey there @witty-keyboard-20400! All browsable entities accept the BrwosePaths aspect to specify their browse path. Some entities also have default browse path behavior. For these entities, if a browse path is not provided, Datahub will generate one for them.
1
We generally advise supplying an explicit BrowsePaths aspect rather than relying on the default behavior because, as you note, it is a bit opaque.
1