[bug] Some UI bug with duplication entities in dataset navigation menu

[YuriyGavrilov]

Describe the bug

Every time receive such bug as dublication of hierarchy tree. It looks like this:

or this

or this

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior So it is difficult to manage. need to delete errors and ingest again. Main things is that there is a need to regenerate dataset urn. urn should be uniq. and there should be no such case sensitive bug when dataset created on different ways.

Screenshots see above

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 0.11]

Additional context I think hierarchy of datasets could be managed by datahub not only by ingestion. or may be in the ingestion but on more proper and defined way.

[remisalmon]

Duplicate of https://github.com/datahub-project/datahub/issues/9276.

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io

[YuriyGavrilov]

Still not fix it

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io

[YuriyGavrilov]

It is actual

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io

[Naralas]

Hi, I am facing the exact same issue, any update regarding that ? OS: Windows Browser: Chrome Version: 0.11

By querying the browse paths of some entities in the respective duplicate folders we can see they are tied to the same objects in the backend, e.g.

Paths for entity 1:

{
  "value": {
    "__type": "BrowsePathsV2",
    "path": [
      {
        "id": "urn:li:container:dc265c4ac9b44e9fb39446d055c38630",
        "urn": "urn:li:container:dc265c4ac9b44e9fb39446d055c38630"
      },
      {
        "id": "urn:li:container:1a1608e5f211201df9a09cbbe86ce32b", 
        "urn": "urn:li:container:1a1608e5f211201df9a09cbbe86ce32b"
      }
    ]
  }
}

Paths for entity 2:

{
  "value": {
    "__type": "BrowsePathsV2",
    "path": [
      {
        "id": "urn:li:container:dc265c4ac9b44e9fb39446d055c38630",
        "urn": "urn:li:container:dc265c4ac9b44e9fb39446d055c38630"
      },
      {
        "id": "urn:li:container:1a1608e5f211201df9a09cbbe86ce32b",
        "urn": "urn:li:container:1a1608e5f211201df9a09cbbe86ce32b"
      }
    ]
  }
}

So it looks like it's an issue on the frontend side

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io

[YuriyGavrilov]

@github-actions This is not stale. Just nobody wants to fix it :(

[jason4zhu]

Hi, just wanna catch up, does this issue fixed in the latest version 0.13.3? Thanks!

[hhhsir0123]

We're facing the save issue as well in verison 0.12.x, could anyone help solving? I'll appreciate that.

[aphonsoar]

Faced the same problem on version v0.13.2

[YuriyGavrilov]

Also have this, with Tableau, oracle, vertica, Postgres ..

[hsheth2]

This was largely resolved by https://github.com/datahub-project/datahub/pull/9613 in the 0.13.0 release. This requires that both DataHub and the datahub CLI are using versions newer than 0.13.0.

If you previously ingested an entity using an older version of datahub, you will need to rerun ingestion in order to correct this issue. Any entities that are not ingested in that new run may not be corrected - you can check the "last synchronized" timestamp in the UI to validate that things have been ingested.

Finally, in certain cases, this happens due to a desynchronization between mysql and elasticsearch. If the browsePathsV2 aspect in mysql contains container urns, but the browsePathsV2 field in Elastic does not, then using restore indicies will fix that.

[vejeta]

The issue is still present in 0.13.0. We performed a new reindex starting from a clean install, so there is no previously ingested entities.

I can't say yet for 0.14.x.

I will update here after we perform a index restoration (again) or upgrade to 0.14.x