[JBoss JIRA] (TEIID-3429) Provide hooks to interrogate metadata prior to full import
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3429?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3429:
-------------------------------------
>However if we are going that far, then it may be just as well to not route this logic through the translator at all and just introduce some light weight remoting logic such that the Designer can >get at the metadata facilities of the relevant connection directly.
No, we do not want to manage another layer like translators for metadata.
Let me iterate the flow from view of Designer you are saying
1) Designer --> makes a admin connection
2) Designer --> deploys a dummy vdb that does not do metadata load
3) Designer --> makes JDBC connection
4) Designer --> using jdbc connection queries "getCatalog", then "getSchema", then "getTables" etc.
5) Designer --> makes it's selections and creates a new metadata vdb, deploys using the admin connection
6) Designer --> then using the Admin connection, retrieves the DDL using "getSchema" method.
7) Designer --> builds model.
For (2) you will be developing a new MetadataFactory that understands the translator level "getCatalog" kind methods. or modify the DDL Metadata Factory to do the same with help of some flag. I thought using both JDBC and Admin interfaces for what looks like single task for user prespective is not good. Other than that I do not have any other objections
> Provide hooks to interrogate metadata prior to full import
> -----------------------------------------------------------
>
> Key: TEIID-3429
> URL: https://issues.jboss.org/browse/TEIID-3429
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> To support the Desinger we should offer the ability to interrogate metadata prior to full import.
> Exploring metadata is effectively an entirely different mode of operation with respect to the current metadata processing logic on the Teiid side. Also partial metadata isn't something that would neatly be expressed through DDL - tables without columns, a list of schema names, etc.
> Ways around that would be to expose source procedures for metadata interrogation:
>
> getTableNames - which would probably give both the Teiid name and the name in source and consider the current translator metadata settings
> getProcedureNames
> And importer specific info such as for JDBC getTableTypes, getCatalogNames, getSchemaNames
>
> I'd want to keep it fairly high level though. Getting column or key information I'd expect would be done through the normal full import.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIID-3464) Inline scalar with clauses
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3464?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3464:
----------------------------------
Description:
A query of the form:
WITH t\(n) AS ( select 1 ) SELECT ...
should inline the the with rather than evaluating separately.
was:
A query of the form:
WITH t(n) AS ( select 1 ) SELECT ...
should inline the the with rather than evaluating separately.
> Inline scalar with clauses
> --------------------------
>
> Key: TEIID-3464
> URL: https://issues.jboss.org/browse/TEIID-3464
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.11
>
>
> A query of the form:
> WITH t\(n) AS ( select 1 ) SELECT ...
> should inline the the with rather than evaluating separately.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 1 month
[JBoss JIRA] (TEIID-3464) Inline scalar with clauses
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3464:
-------------------------------------
Summary: Inline scalar with clauses
Key: TEIID-3464
URL: https://issues.jboss.org/browse/TEIID-3464
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.11
A query of the form:
WITH t(n) AS ( select 1 ) SELECT ...
should inline the the with rather than evaluating separately.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 1 month
[JBoss JIRA] (TEIID-3371) Upgrade Teiid with EAP 6.4 Alpha
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3371?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-3371.
---------------------------------
Labels: Beta2 (was: )
Resolution: Done
Used CR25 BOM version. There were only few minor conflicts. One major I consider is SOLR version is 3.6 in EAP, and Teiid uses 4.5.0. I kept the overloaded one, but the may cause some product issues.
- Arquillian tests run cleanly.
- I also adopted the module layout structure closely resemble to the product version.
- The Saxon, GeoSpatial libraries are moved into their own module files, away from the Teiid's module and then defined as module dependencies.
> Upgrade Teiid with EAP 6.4 Alpha
> --------------------------------
>
> Key: TEIID-3371
> URL: https://issues.jboss.org/browse/TEIID-3371
> Project: Teiid
> Issue Type: Enhancement
> Components: Build/Kits
> Affects Versions: 8.11
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Labels: Beta2
> Fix For: 8.11
>
> Attachments: diff.txt, status.txt
>
>
> Upgrade all the Teiid projects to be built based on EAP 6.4 Alpha. Currently, this would align with jboss-integration-platform-bom 6.0.0.CR25 and EAP Alpha version 7.5.0.Final-redhat-17. Note, 7.5.0.Final-redhat-17 is the version in the EAP kit, but only CR25 bom is available.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 1 month
[JBoss JIRA] (TEIID-3343) Add classification to jboss module.xml files
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3343?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-3343.
---------------------------------
Labels: Beta2 (was: )
Resolution: Done
Added the classifications to all the modules contributed as part of Teiid install
> Add classification to jboss module.xml files
> --------------------------------------------
>
> Key: TEIID-3343
> URL: https://issues.jboss.org/browse/TEIID-3343
> Project: Teiid
> Issue Type: Task
> Components: Build/Kits
> Affects Versions: 8.11
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Labels: Beta2
> Fix For: 8.11
>
>
> Add classification to the module.xml files that are private or unsupported.
> example for private modules:
> <properties>
> <property name="jboss.api" value="private"/>
> </properties>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 1 month
[JBoss JIRA] (TEIID-3281) MongoDB: EmptyStackException when joining tables
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3281?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3281:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1180144|https://bugzilla.redhat.com/show_bug.cgi?id=1180144] from NEW to ASSIGNED
> MongoDB: EmptyStackException when joining tables
> ------------------------------------------------
>
> Key: TEIID-3281
> URL: https://issues.jboss.org/browse/TEIID-3281
> Project: Teiid
> Issue Type: Bug
> Components: Connector API
> Affects Versions: 8.7
> Reporter: Filip Elias
> Assignee: Ramesh Reddy
> Labels: CR2
> Fix For: 8.10
>
> Attachments: mongodb-vdb.xml, server.log
>
>
> Teiid throws java.util.EmptyStackException when joining data from table which has teiid_mongo:MERGE property enabled.
> Example:
> {code}
> insert into customer2 values(1,'Pepa', 'Koukal');
> insert into customer2 values(2,'Jan', 'Tlemil');
> insert into Address values(1,1,'Pepas Street','Pepas City','Pepas State', 'Pepas zipcode');
> insert into Address values(2,2,'Jans Street','Pepa','Jans State', 'Jans zipcode');
> {code}
> {code}
> select a.*,b.* from customer2 a inner join Address b on a.CustomerId=b.CustomerId order by a.customerID
> {code}
> {code}
> Error:
> java.util.EmptyStackException
> at java.util.Stack.peek(Stack.java:102)
> at java.util.Stack.pop(Stack.java:84)
> at org.teiid.translator.mongodb.MongoDBSelectVisitor.visit(MongoDBSelectVisitor.java:993)
> at org.teiid.language.SortSpecification.acceptVisitor(SortSpecification.java:53)
> at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51)
> at org.teiid.translator.mongodb.MongoDBSelectVisitor.append(MongoDBSelectVisitor.java:112)
> {code}
> VDB and log are in the attachment.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 1 month