Okera manages data access and governance, not storage, per se. Yet as a matter of course, the platform does provide much of the functionality you may expect from conventional databases but is not found in Big Data infrastructure. Okera maintains a schema registry that maps datasources, objects, and fields similarly to some features of relational database management systems (RDBMSes). See Okera Catalog Overview for more.
Articles in this section
- Is there a way to not store passwords in the env.sh file?
- How does Okera ensure container security?
- Planner/Worker Separation
- Can the okera token specify more than one group?
- Users facing token issue while spark-submit in cluster mode
- Can an existing non-ODAS enabled EMR be upgraded in place to talk to an ODAS cluster?
- What is Okera?
- Why do I need Okera?
- How do I use Okera?
- Is Okera a database?