• Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Major Major
    • Open To Community
    • None
    • JDBC Connector
    • None

      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.

            [TEIID-3898] Add OrientDB translator

            It can be left open in the Open To Community bucket.

            Steven Hawkins added a comment - It can be left open in the Open To Community bucket.

            Thanks dkrapohl@hotmail.com! rhn-engineering-shawkins, do you want to close the issue in such a case?

            Rafal Korytkowski (Inactive) added a comment - Thanks dkrapohl@hotmail.com ! rhn-engineering-shawkins , do you want to close the issue in such a case?

            rkorytkowski we moved away from OrientDB so we wouldn't need it ourselves. I can reject the ticket unless you have other requests for it.

            Donald Krapohl (Inactive) added a comment - rkorytkowski we moved away from OrientDB so we wouldn't need it ourselves. I can reject the ticket unless you have other requests for it.

            dkrapohl@hotmail.com, would you still be interested in this feature?

            Rafal Korytkowski (Inactive) added a comment - dkrapohl@hotmail.com , would you still be interested in this feature?

            > Noticed this neat trick in the JPA translator to only push down joins on foreign keys.

            Yes, several of the hierarchical sources have that requirement. See salesforce also, which has to produce valid SOQL queries.

            > Maybe as predicate functions in the where clause?

            We have similar logic in the Modeshape translator, which has JCR constructs that are effectively predicates, but need special handling in the translator.

            Steven Hawkins added a comment - > Noticed this neat trick in the JPA translator to only push down joins on foreign keys. Yes, several of the hierarchical sources have that requirement. See salesforce also, which has to produce valid SOQL queries. > Maybe as predicate functions in the where clause? We have similar logic in the Modeshape translator, which has JCR constructs that are effectively predicates, but need special handling in the translator.

            SQL reference here. Looks like next version (2.2) will have OGC spatial support (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.

            setSupportedJoinCriteria(SupportedJoinCriteria.KEY);
            

            Not sure yet how to map some of the graph concepts. Maybe as predicate functions in the where clause?

            Tom Arnold (Inactive) added a comment - SQL reference here . Looks like next version (2.2) will have OGC spatial support (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. setSupportedJoinCriteria(SupportedJoinCriteria.KEY); Not sure yet how to map some of the graph concepts. Maybe as predicate functions in the where clause?

            Adding into the open to community bucket. The earliest a core dev could pick this up would be for 9.1. Any additional design considerations or goals (for example what is most pressing to support beyond having the generic ansi translator) will help.

            Steven Hawkins added a comment - Adding into the open to community bucket. The earliest a core dev could pick this up would be for 9.1. Any additional design considerations or goals (for example what is most pressing to support beyond having the generic ansi translator) will help.

              Unassigned Unassigned
              dkrapohl@hotmail.com Donald Krapohl (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: