Skip to main content

OReva - Fork of OData4J library

Teiid community depends upon OData4J for its V2 implementation of the OData protocol. We see that there has been not much activity in OData4J project for last 2 years, so we consider this is project is effectively dead by all means. However, Teiid community still on hook to support our OData V2 implementation for little while longer (I see at least 2 yrs), for that reason we have forked this project and calling it "OREVA".

I have somewhat simplified the offering by removing the JDBC and JPA as we do not use those modules, but rest of core protocol is intact. We will try to keep it up with any bug fixes and maintenance. So, if you are wanting to submit a patch or work on some enhancements you can always come and talk to us,  patches are Welcome.

Here is the fork https://github.com/teiid/oreva   If there is enough interest form OData4J remaining community, I do not mind moving this to different GitHub organization other than Teiid. If you find a issue, use https://github.com/teiid/oreva/issues  for now we are using Teiid's issues system.

I also would like to thank John Spurlock for his all his contributions towards OData4J, Thank you. It is a very good OData framework

Thank you.

Ramesh..
http://teiid.org

Comments

  1. It's nice of you to continue working on it.

    Have you proposed to John Spurlock of taking over the odata4j project? That way you'll simply create a new version... and less confusion for the community.

    Thanks!

    ReplyDelete
  2. This comment has been removed by a blog administrator.

    ReplyDelete
  3. No. As I mentioned, this came out our necessity to support the library for Teiid project. Right now, I do not have any aspirations without broader community support to take beyond V2, as most of my time goes to supporting Teiid project. I am also a commiter on Apache Olingo for V4. Even though this may look like I am trying to segment the OData4J community that not all my intentions. I wanted to start something new that I can manage the way from what I learned from Teiid, may that be tools, infrastructure etc need to a run a project that I am comfortable and have control over it.

    I just heard from one of Teiid community member that, they are going to contribute to OData V3 version to OReva, that is a great news for us. I hop I can keep the momentum up.

    ReplyDelete
  4. And also do not forget, I removed the JPA and JDBC interfaces from the library, IMO they do not belong core library, they need to be sub-projects. I know JPA is popular with lot of community members, but in itself is lot of work to maintain.

    ReplyDelete

Post a Comment

Popular posts from this blog

Teiid Platform Sizing Guidelines and Limitations

Users/customers always ask us about the sizing of their Data Virtaulization infrastructure based on Teiid or the JDV product from Redhat. Typically this is very involved question and not a very easy one answer in plain terms. This is due to fact that it involves taking into consideration questions like:
What kind of sources that user is working with? Relational, file, CRM, NoSQL etc.How many sources they are trying to integrate? 10, 20, 100?What are the volumes of data they are working with? 10K, 100K, 1M+?What are the query latency times from the sources? How you are using Teiid to implement the data integration/virtualization solution. What kind of queries that user is executing? Even small federated results may take a lot of server side processing - especially if the plan needs tweaking.Is materializing being used?Is query written in optimal way?and so on..Each and every one of the question affects the performance profoundly, and if you got mixture of those then it become that much…

Teiid Runtimes Explained

If you have been following Teiid lately we have been going through a whole lot of renovations. Yes, renovations or reorganization or refactoring or whatever you want to call it. Basically, we are making Teiid more modular with fewer dependencies that can be used by however your use case dictates rather than use it as one monolith application deployed into WildFly JEE Application Server. There is nothing wrong in using Teiid as server model, but with the proliferation of container-based workloads and cloud-based architectures, the previous server-based model does not work or simply won't scale. So, we needed to think of alternatives, thus Teiid team introduced a couple different versions modular Teiid what we are calling as "Teiid Runtimes".

Note that in these modular Teiid runtimes, not all the features you were used to using in Teiid Server model may not be there but you will have extensions to add in those that are most appropriate for your domain. If you are looking …