5:53 a.m.
All,
I've been trying to clarify 7.x Teiid Designer goals and tasks.....and here's my
starting point for discussion:
Release 7.0 - Target Date: March, 2010
Primary goal: make changes necessary to maintain compatibility with Teiid 7.0 release and
in particular, JCA-related changes. Tasks will include:
• Inherit miscellaneous code no-longer needed by Teiid, but still used within Designer
( completed )
• Changes to connector/driver framework required to accommodate JCA changes within
Teiid relating to VDB packaging and execution.
• Maintain current Preview Data and Execute VDB functionality.
Release 7.1 - Target Date: June, 2010
Primary Goal: Simplify integration with Eclipse tooling and reduce code-base by replacing
functionality by utilizing available/existing open source work, in particular, DTP and
it's Data Source and Connector Profile frameworks and reduce or remove dependency on
embedded Teiid.
• Change Designer's JDBC import to utilize Eclipse's DTP data sources and
connection profiles.
• Replace Designer's SQL Explorer (and possibly Preview Data) functionality via
VDB-to-server deployment and DTP query execution.
Barry LaFond
Teiid Designer Project
6:35 a.m.
On Jan 26, 2010, at 2:53 PM, Barry Lafond wrote:
Release 7.1 - Target Date: June, 2010
Change Designer's JDBC import to utilize Eclipse's DTP data sources and
connection profiles.
This may also affect the Connection/Model Binding views
Replace Designer's SQL Explorer (and possibly Preview Data)
functionality via VDB-to-server deployment and DTP query execution.
"VDB-to-server deployment" implies we're looking at removing Teiid as an
embedded server within Designer and replacing it with the ability to connect to an
already-installed Teiid server (also keeping in mind we intend to bundle a Teiid server
with the JBDS product offering).
Thanks,
JPAV
6:46 a.m.
On Tue, 2010-01-26 at 15:53 -0500, Barry Lafond wrote:
* Maintain current Preview Data and Execute VDB functionality.
Unless you are thinking to maintain both Teiid 6.2 along with Teiid 7.0
in the designer this is not possible.
Teiid 7.0 does NOT support embedded version, nor does it work out side
the container.
* Replace Designer's SQL Explorer (and possibly Preview
Data)
functionality via VDB-to-server deployment and DTP query
execution.
Once you integrate with DTP tools, this view is given
automatically,
replacing the SQLExplorer, provided we create a Teiid connection
profile. This is already being worked by jdoyle.
Ramesh..
6:59 a.m.
On Jan 26, 2010, at 3:46 PM, Ramesh Reddy wrote:
On Tue, 2010-01-26 at 15:53 -0500, Barry Lafond wrote:
> * Maintain current Preview Data and Execute VDB functionality.
Unless you are thinking to maintain both Teiid 6.2 along with Teiid 7.0
in the designer this is not possible.
Teiid 7.0 does NOT support embedded version, nor does it work out side
the container.
No, we're not planning on maintaining 6.2. The idea, which we still believe is
possible, is to auto-build and deploy VDBs under the covers that contain artifacts from
the workspace, build an appropriate DTP profile, etc., then use DTP's existing preview
capability against that Teiid source.
> * Replace Designer's SQL Explorer (and possibly Preview Data)
> functionality via VDB-to-server deployment and DTP query
> execution.
Once you integrate with DTP tools, this view is given automatically,
replacing the SQLExplorer, provided we create a Teiid connection
profile. This is already being worked by jdoyle.
We're aware of John's work; the purpose of this posting is to inform the rest of
the community as to our intentions wrt to releases. Plus, John's work doesn't
cover all aspects of what we're discussing (see above). Finally, the DTP view that is
"given automatically" doesn't just show up in Designer automatically -
we're still anticipating some development work necessary to ensure the user experience
remains as seamless as possible and to reduce any drastic changes to how things work now.
Thanks,
JPAV
7:07 a.m.
----- "John Verhaeg" <jverhaeg(a)redhat.com> wrote:
On Jan 26, 2010, at 3:46 PM, Ramesh Reddy wrote:
> On Tue, 2010-01-26 at 15:53 -0500, Barry Lafond wrote:
>
>> * Maintain current Preview Data and Execute VDB functionality.
> Unless you are thinking to maintain both Teiid 6.2 along with Teiid 7.0
> in the designer this is not possible.
>
> Teiid 7.0 does NOT support embedded version, nor does it work out side
> the container.
>
No, we're not planning on maintaining 6.2. The idea, which we still believe is
possible, is to auto-build and deploy VDBs under the covers that contain artifacts from
the workspace, build an appropriate DTP profile, etc., then use DTP's existing preview
capability against that Teiid source.
Barry: "Under the covers" means replacing the current designer "runtime
query metadata" with a standard (hidden) VDB..... dang, this sounds like Dimension.
>
>> * Replace Designer's SQL Explorer (and possibly Preview Data)
>> functionality via VDB-to-server deployment and DTP query
>> execution.
> Once you integrate with DTP tools, this view is given automatically,
> replacing the SQLExplorer, provided we create a Teiid connection
> profile. This is already being worked by jdoyle.
We're aware of John's work; the purpose of this posting is to inform the rest of
the community as to our intentions wrt to releases. Plus, John's work doesn't
cover all aspects of what we're discussing (see above). Finally, the DTP view that is
"given automatically" doesn't just show up in Designer automatically -
we're still anticipating some development work necessary to ensure the user experience
remains as seamless as possible and to reduce any drastic changes to how things work now.
Thanks,
JPAV
7:20 a.m.
On Tue, 2010-01-26 at 17:07 -0500, Barry Lafond wrote:
> No, we're not planning on maintaining 6.2. The idea, which
we still
believe is possible, is to auto-build and deploy VDBs under the covers
that contain artifacts from the workspace, build an appropriate DTP
profile, etc., then use DTP's existing preview capability against that
Teiid source.
Barry: "Under the covers" means replacing the current designer
"runtime query metadata" with a standard (hidden) VDB..... dang, this
sounds like Dimension.
Cool! This is even better. I was under the impression that this was not
possible based on the original preview functionality discussions.
Note that each time you update the VDB in the Teiid Container, the
previous one is un-deployed and the new one deployed. This could be
little heavy weight (slow).
7:28 a.m.
----- "Ramesh Reddy" <rareddy(a)redhat.com> wrote:
On Tue, 2010-01-26 at 17:07 -0500, Barry Lafond wrote:
> > No, we're not planning on maintaining 6.2. The idea, which we still
> believe is possible, is to auto-build and deploy VDBs under the covers
> that contain artifacts from the workspace, build an appropriate DTP
> profile, etc., then use DTP's existing preview capability against that
> Teiid source.
>
> Barry: "Under the covers" means replacing the current designer
> "runtime query metadata" with a standard (hidden) VDB..... dang, this
> sounds like Dimension.
Cool! This is even better. I was under the impression that this was not
possible based on the original preview functionality discussions.
Note that each time you update the VDB in the Teiid Container, the
previous one is un-deployed and the new one deployed. This could be
little heavy weight (slow).
Note that this is projected to be a 7.1 or later task and NOT 7.0, so we still have deal
with teiid embedded AND runtime query metadata for preview.
7:49 a.m.
There is work to be done to get the run time metadata working, if you
are thinking about throwing that away in the next dot release, I would
recommend we need to take second look at this requirement.
On Tue, 2010-01-26 at 17:28 -0500, Barry Lafond wrote:
----- "Ramesh Reddy" <rareddy(a)redhat.com> wrote:
> On Tue, 2010-01-26 at 17:07 -0500, Barry Lafond wrote:
> > > No, we're not planning on maintaining 6.2. The idea, which we
still
> > believe is possible, is to auto-build and deploy VDBs under the
covers
> > that contain artifacts from the workspace, build an appropriate
DTP
> > profile, etc., then use DTP's existing preview capability against
that
> > Teiid source.
> >
> > Barry: "Under the covers" means replacing the current designer
> > "runtime query metadata" with a standard (hidden) VDB..... dang,
this
> > sounds like Dimension.
>
> Cool! This is even better. I was under the impression that this was
not
> possible based on the original preview functionality discussions.
>
> Note that each time you update the VDB in the Teiid Container, the
> previous one is un-deployed and the new one deployed. This could be
> little heavy weight (slow).
>
>
Note that this is projected to be a 7.1 or later task and NOT 7.0, so
we still have deal with teiid embedded AND runtime query metadata for
preview.
5224
days inactive
5224
days old
teiid-designer-dev@lists.jboss.org
7 comments
3 participants
participants (3)
-
Barry Lafond -
John Verhaeg -
Ramesh Reddy