Oracle view metadata only ingested with select privilege about openmetadata

[ayush-shah]

The above is expected behavior.
we are planning to modify the usage with DBA_ to ALL_ due to the DBA priviedges issues faced by many. Rather using a ALL_ would help nullify the problem and the data can be fetched where the user have priviledges

[arubincs]

Thank you. I was confused that the Oracle connector documentation says

-- GRANT SELECT CATALOG ROLE PRIVILEGE TO FETCH METADATA TO ROLE / USER
GRANT SELECT_CATALOG_ROLE TO new_role;

and

With just these permissions, your user should be able to ingest the schemas, but not the tables inside them.

I thought that SELECT_CATALOG_ROLE is all that's necessary for ingesting Oracle object metadata. And it is consistent with how table and stored procedures are treated in OpenMetadata. Why are views handled differently in 1.3.x?

In future releases, will SELECT privileges (meaning the object is visible in an ALL_ dictionary) be necessary to ingest schemas?