]
Tom Arnold commented on TEIID-3898:
-----------------------------------
SQL reference [
]. Looks like next version (2.2)
will have [OGC spatial
] (like
PostGIS).
Seems kind of like JPQL. Metadata processor could map "classes" as tables, and
"links" as foreign keys.
Noticed this neat trick in the JPA translator to only push down joins on foreign keys.
{code}
setSupportedJoinCriteria(SupportedJoinCriteria.KEY);
{code}
Not sure yet how to map some of the graph concepts. Maybe as predicate functions in the
where clause?
Add OrientDB translator
-----------------------
Key: TEIID-3898
URL:
https://issues.jboss.org/browse/TEIID-3898
Project: Teiid
Issue Type: Feature Request
Components: JDBC Connector
Reporter: Don Krapohl
Fix For: Open To Community
My organization has high-performance analytics on OrientDB graph databases. We use Teiid
for centralized governance, access, etc. It would be beneficial to us if Teiid could
translate to the SQL-like OrientDb syntax. Because there are many SQL-like syntax
components of OrientDB's REST endpoints this should be fairly straightforward.
The OrientDB site is
http://orientdb.com/. It's Apache 2 licensed, has a stable and
mature community, has multiple releases, and provides multiple access methods (jdbc, odbc,
REST). Work on the translator should not be wasted effort.
I can assist with testing if it would be helpful and if the translator is started I can
assist in dev.