Hey everyone!, I have a question about the UI of P...
# getting-started
b
Hey everyone!, I have a question about the UI of Properties Tab in Dataset Page. When we add dataset that has siblings in it, Then in properties tab it shows both siblings custom properties as well as the custom properties of its own • Why it is doing that? Is there any particular benefits or side effects? • Because • If user want to see custom-properties of the sibling then user can • simply see by visiting the properties tab through indivisual sibilings ◦ i.e inside Composed Of • If we have more then one siblings, then which one will we show in properties tab? Ref PR https://github.com/datahub-project/datahub/pull/5390
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: 1️⃣ There's a lot of good information on our docs site: www.datahubproject.io/docs, Have you searched there for a solution? Yes button 2️⃣ It's not uncommon that someone has run into your exact problem before in the community. Have you searched Slack for similar issues? Yes button
m
@brave-mouse-33819: the sibling feature creates a composite entity and merges the attributes from all the siblings into the composite entity. As a result, you see the properties map getting merged. Like you said, since each entity has its own separate page, you could view them independently and in that case the properties tab will only include properties from that specific entity. I guess it is not clear to me what the specific problem is that you are pointing out.
b
@mammoth-bear-12532 @big-carpet-38439, Basically I am trying to understand that why we are doing the following thing i.e. Let say we have
customProperties
in an object and as well as
customProperties
inside the sibling i.e.
Copy code
{
  properties:{
       customProperties:{} //----> A
  },
  siblings: {
     siblings:[
          properties:{
               customProperties:{} //--> B
           }
     ]
  }
}
And we are combining both as given below, So my question is why are we doing that? Is there any benefit to it, and what if we have more than one siblings so which it will show in the properties tab
b
It will show all of the sibling properties merged into one!
This is intentional, as a sibling represents a composite entity comprised of multiple underlying entities