open-metadata / openmetadata Goto Github PK

We should display
Tier 1
Tier 2
Tier 3
Tier 4
Tier 5

Even if the aggregations are not returned for all of them. Lets display all of those labels when the counts are available show those counts otherwise it should be set to 0

Enable the following Sort by fields: sort usage, sort by following

Also, change the references to the new github repo.

Example:
GET teams?field=users returns a list of users in the team as entityReference. But entityReference does not have fields to return user profile.

@Sachin-chaurasiya FYI... A bug to track the request you made in issue #98

If the API requesting table information is passing a field like "owners". We should return owners filed as we do today and include "ownedByMe" in extra fields.

1. If the logged-in user is owned dataset returns true
2. if the team is owned and logged in user belongs to the tam return true
3. for all other cases we should return false.

records_produced gives an error

{'name': 'resource.type', 'type': String(), 'nullable': True, 'comment': None, 'default': None, 'precision': None, 'scale': None, 'max_length': None}

Example in jdbcConnection.json:
https://github.com/StreamlineData/catalog/blob/master/catalog-rest-service/src/main/resources/json/schema/type/jdbcConnection.json

Change all such reference in the generated doc to from StreamlineData/catalog to Open-Metadata/openmeatadata.

Scripts and commands to run ingestion on docker container are outdated and need modifications to run.

Currently, we are getting only these 4 fields for owns and 5 fields for users

owns:[
   {
      "id": "155ce023-843e-4b4b-a6bc-10d989d4182f",
      "type": "table",
      "name": "users",
      "href": "http://localhost:8585/api/v1/tables/155ce023-843e-4b4b-a6bc-10d989d4182f"
    },
],
users:[
{ 
     "description": "Robert Cole"
    "href": "http://localhost:8585/api/v1/users/03a8a9ac-e29b-4a9a-8ad1-00339b849310"
    "id": "03a8a9ac-e29b-4a9a-8ad1-00339b849310"
    "name": "robert_cole6"
    "type": "user"
}
]

 1. use case: FQN to redirect users from team page to dataset details page 
 2. use case: Profile to show user profile pic beside the username

@sanketbambulkar we need to come up with standard pages when there is no data to show and fonts etc..

In Manager or description dialog boxes, we do not show any hints that the user actions are getting saved

It's really confusing to me as a user. Let's do something similar to the below
https://uxmag.com/sites/default//files/Uxmag-articles/2020-Articles/Microinteractions/Microinteractions2.gif

We are now going to show some stats and links on the homepage.

Refer Figma: https://www.figma.com/file/VaeQD2fIhQVDCvqBHyEv7J/Streamline-Untitled?node-id=4856%3A3048

Docs link should go to docs.open-metadata.org
APIs link should go to /swagger.html

Include filtering the search results by Asset Type with two choices Table & Database.

@parthp2107 Let's add Auth0 Implementation similar to what we have done for the JWT filter
https://github.com/auth0/auth0-java

APIs returning following

UI displays

1. Provide an API to claim an entity such as (database, table)
2. We will not allow other users to claim a table if there is an owner and active. Transfer of ownership needs to be thought through and can come in later.
3. If there is no owner is associated with a table anyone can claim it.

There are two versions of the tests. Secure tests with authentication and non-secure tests with no authentication. Merging them together into a single version of tests that always require authentication.

Github workflow - pylint throwing fatal errors in Workflow process

Page is already added, need content to replace with Lorem Ipsum.

Need to change catalog string to openmetadata in the following places:

• DB Name and Credentials
• Final package name
• Yaml file name
• Server start filename

• Internal links are not working
• MySql steps are outdated (verify with @parthp2107 )

Patch API : api/v1/tables/

Payload:

[{"op":"replace","path":"/tags/0/tagFQN","value":"Tier.Tier3"}]

Response:

{
  "id": "338fe5bb-b125-4ba6-aa61-313b29e9947d",
  "name": "sql_sizing_profiles",
  "href": "http://localhost:8585/api/v1/tables/338fe5bb-b125-4ba6-aa61-313b29e9947d",
  "fullyQualifiedName": "aws_redshift.information_schema.sql_sizing_profiles",

  <----------Other_fields------------->

  "tags": [
    {
      "tagFQN": "Tier.Tier1",
      "labelType": "Manual",
      "state": "Confirmed"
    },
    {
      "tagFQN": "Tier.Tier3",
      "labelType": "Manual",
      "state": "Confirmed"
    }
  ]
}

Expected behaviour:
Response should only have 1 Tier set, i.e. Tier3 in this case

/api/v1/search/query?q=***%20AND%20followers:8a98906b-c636-4df8-be60-03318c365cf8&from=0&size=10

you only need to pass q=*
for text you need to add q=*text*

• If no data is found under any module, then show consistent 404 error
• If page link is broken then show proper 404 error

In the above example, we have a users table from MySQL and a users table from redshift. Can't tell the difference here, good to have a service type icon next to them.