Teiid 7.5 alpha1
by Steven Hawkins
Given the short timeline for 7.5 I'd like to get the first alpha out on Friday. Let me know if you have any concerns.
Steve
13 years
7.4 patch
by Steven Hawkins
After more testing on 7.4 I'm thinking that a one-off patch would be appropriate to post in the download section to address the following:
TEIID-1592 - cluster event distribution broken
TEIID-1593 - create temp table broken
TEIID-1595 - implicit create not checked against roles
TEIID-1597 - procedures broken in multi-source and xml staging tables not resolvable
This would not be a 7.4.1 release, just a patch to be placed in the appropriate profile/lib directory. No further patches should be issued.
As for subsequent releases, the versions in JIRA have been updated to reflect a 7.5 release in late July that will consist mostly of bug fixes, and a 8.0 release following fairly closely based upon the pending release of AS 7.0.
The Teiid Team
13 years
Ready for 7.4 release
by Steven Hawkins
Hello all,
I am going to start the 7.4 release process. A merge to trunk is still pending. At least for now trunk is designated as 7.5.
Thanks,
Steve
13 years
Teiid 7.4 release
by Steven Hawkins
Hello all,
As there are no unresolved issues remaining in 7.4 and CR1 has been posted for a week, are there any objections to performing the release tomorrow?
Steve
13 years
branching today
by Steven Hawkins
Hello all,
We'll start a 7.4.x branch today. Trunk will tentatively be called 7.5. I'll also create a 7.5 version in JIRA for issues that are worked. Depending upon what we work out for a release schedule, we'll convert 7.5 into 8.0 if needed. For now we'll perform merges to migrate any change, there's no need to commit to both branches yet.
Steve
13 years
REST Interface to TEIID
by Ted Jones
We have been wrestling with the best way to implement a RESTFul interface to a VDB. Here are the options we have come up with to date:
1. Create a hook to procedures to allow a mapping from HTTP verbs to procedures in a model within a VDB. This war would be generated from Designer and there would be one war per VDB.
Example... if I have a procedure name rgetBooks() the procedure would map to a GET at URI=/books and would return all books (assuming that the procedure was written correctly)
2. Create a single war that would have pre-defined URIs for table access for any JDBC connection. Multiple connections could be supported within the same war based on the URI. The JNDI names would be entered by the user in a properties file or some analogous mechanism.
Example URI=/{dbschema}/{catalog}/{table}?column1=value would return the record corresponding to "value" in the target table
Procedures could also be supported in this manner.
3. Another option would be to generate the war discussed in option 2 from Designer to eliminate the need for the user to hand edit a properties file.
There are pros and cons for all the options. 1 puts more onus on the user but 2/3 are definitely the more complicated solutions and they require intimate knowledge of the underlying metadata.
Please respond with your feedback on these proposed solutions and feel free to add other alternatives.
Thanks,
Ted
13 years
Teiid 7.4 CR1
by Steven Hawkins
Hello all,
We should be ready for a CR1 by tomorrow. There has been quite a lot of functionality added so I would expect that we'll need a full week until the final release.
I'm finishing up code an doc updates related to cache invalidation and metadata updates. Let me know if you have anything that should hold up the CR build.
Steve
13 years, 1 month
