[JBoss JIRA] (TEIID-2902) More incremental join when a limit is present
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2902?page=com.atlassian.jira.plugin... ]
Work on TEIID-2902 started by Steven Hawkins.
> More incremental join when a limit is present
> ---------------------------------------------
>
> Key: TEIID-2902
> URL: https://issues.jboss.org/browse/TEIID-2902
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.7
> Reporter: Ivan Chan
> Assignee: Steven Hawkins
> Fix For: 8.8
>
>
> For SQL like:
> SELECT
> t1.column1,
> t2.column1
> FROM
> schema1.table1 t1,
> schema2.table1 t2
> WHERE
> t1.column2=t2.column2
> LIMIT 100
> Teiid may get the whole schema1.table1 content and the whole schema2.table1 content, do the join in memory and then, limit the resultset to 100 records.
> However, I think teiid can fetch smaller set of data then do a join. If the join result set is less than number of rows asking, keep fetching next set of data and do a join until hits the limit number.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIID-2932) Datastax: fail to access PortfolioDemo (demo schema that provided by Datastax)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2932?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2932:
----------------------------------
Fix Version/s: 8.8
We'll look into this more for 8.8.
> Datastax: fail to access PortfolioDemo (demo schema that provided by Datastax)
> -------------------------------------------------------------------------------
>
> Key: TEIID-2932
> URL: https://issues.jboss.org/browse/TEIID-2932
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.7
> Environment: Datastax with Teiid 8.7 CR
> Reporter: Ivan Chan
> Assignee: Steven Hawkins
> Fix For: 8.8
>
>
> Fail to access PortfolioDemo (demo schema that provided by Datastax) and the the following exception:
> java.lang.NullPointerException
> at org.teiid.metadata.MetadataFactory.addColumn(MetadataFactory.java:204)
> at org.teiid.translator.cassandra.CassandraMetadataProcessor.addColumnsToTable(CassandraMetadataProcessor.java:101)
> at org.teiid.translator.cassandra.CassandraMetadataProcessor.addTable(CassandraMetadataProcessor.java:63)
> at org.teiid.translator.cassandra.CassandraMetadataProcessor.process(CassandraMetadataProcessor.java:50)
> at org.teiid.translator.cassandra.CassandraMetadataProcessor.process(CassandraMetadataProcessor.java:42)
> at org.teiid.translator.ExecutionFactory.getMetadata(ExecutionFactory.java:915)
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:73)
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55)
> at org.teiid.runtime.EmbeddedServer.loadMetadata(EmbeddedServer.java:685)
> at org.teiid.runtime.AbstractVDBDeployer.loadMetadata(AbstractVDBDeployer.java:161)
> at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:635)
> at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:547)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIID-2881) Add support to use DSL when querying remote JDG 6.2
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-2881?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-2881:
------------------------------------
As I'm moving along on this, thought I would post my comments about the MetadataProcessor and what the object to relational mapping will be (which is slightly different than the object translator).
* <p>
* Here are the rules that are being followed to convert an Object to a row.
* </p>
* <li>Class</li>
* Each class is mapped to a table.
* </br>
* <li>Attributes</li>
* Get/Is methods will be become table columns.
* </br>
* <li>One-to-one association</li>
* The classes on both sides will be merged into a one table. The nameInSource for the attributes in the class
* contained within the root class will be assigned based on this format: "getMethod" name + "." + attribute
* </br>
* Example: Person contains Contact (getContact) and Contact has getter method getPhoneNumber
* so the nameInSource for the column would become Contact.PhoneNumber
* </br>
* <li>One-to-many association</li>
* The classes on both sides are mapped to two tables. The root class will have primary key created. The
* table for the "many" side will have a foreign created.
* </br>
* When an attribute is included from the many side (children), the total number of rows will be multiplied by
* by the number of children objects.
* <p>
* <b>Decisions</b>
* <li>User will need to decide what will be the primary key. Will the key to the cache or a real attribute on the root class
* will be used as the primary key.</li>
*
> Add support to use DSL when querying remote JDG 6.2
> ---------------------------------------------------
>
> Key: TEIID-2881
> URL: https://issues.jboss.org/browse/TEIID-2881
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Affects Versions: 8.7
> Reporter: Van Halbert
> Assignee: Van Halbert
>
> Add support for querying remote JDG 6.2 using DSL.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIID-2946) NPE with a join and a dup_remove child
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2946?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2946.
-----------------------------------
Resolution: Done
Added a null check in the prefetch logic
> NPE with a join and a dup_remove child
> --------------------------------------
>
> Key: TEIID-2946
> URL: https://issues.jboss.org/browse/TEIID-2946
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 8.7.1, 8.8
>
>
> A plan structure such as:
> {code}
> JoinNode ... [CROSS JOIN]
> ...
> SortNode ... [DUP_REMOVE]
> {code}
> Will cause an NPE during prefetch:
> {code}
> 28 Apr 2014 05:35:28,574 ERROR [org.teiid.PROCESSOR] (http-CA31/141.202.65.31:30804-2) eA83y/9ZGnji TEIID30019 Unexpected exception for request eA83y/9ZGnji.6: java.lang.NullPointerException
> at org.teiid.query.processor.relational.SourceState.prefetch(SourceState.java:203)
> at org.teiid.query.processor.relational.JoinNode.prefetch(JoinNode.java:231)
> at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:223)
> {code}
> This is an oversight in that we generally are expecting an equi-join (which would incorporate the dup removal processing) or marking the dup remove as dup remove sort (the fully blocking variant).
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIID-2946) NPE with a join and a dup_remove child
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2946:
-------------------------------------
Summary: NPE with a join and a dup_remove child
Key: TEIID-2946
URL: https://issues.jboss.org/browse/TEIID-2946
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Critical
Fix For: 8.7.1, 8.8
A plan structure such as:
{code}
JoinNode ... [CROSS JOIN]
...
SortNode ... [DUP_REMOVE]
{code}
Will cause an NPE during prefetch:
{code}
28 Apr 2014 05:35:28,574 ERROR [org.teiid.PROCESSOR] (http-CA31/141.202.65.31:30804-2) eA83y/9ZGnji TEIID30019 Unexpected exception for request eA83y/9ZGnji.6: java.lang.NullPointerException
at org.teiid.query.processor.relational.SourceState.prefetch(SourceState.java:203)
at org.teiid.query.processor.relational.JoinNode.prefetch(JoinNode.java:231)
at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:223)
{code}
This is an oversight in that we generally are expecting an equi-join (which would incorporate the dup removal processing) or marking the dup remove as dup remove sort (the fully blocking variant).
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIID-2945) disableLocalTxn only works at connection time
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2945:
-------------------------------------
Summary: disableLocalTxn only works at connection time
Key: TEIID-2945
URL: https://issues.jboss.org/browse/TEIID-2945
Project: Teiid
Issue Type: Bug
Components: JDBC Driver
Affects Versions: 7.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.7.1, 8.8
disableLocalTxn only works at connection time (as a url property). It is intended to be an execution property that works post connection time via a set statement.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIID-2650) A jboss server in domain mode does not advertise its teiid runtime-version
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-2650?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-2650:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 982741|https://bugzilla.redhat.com/show_bug.cgi?id=982741] from NEW to CLOSED
> A jboss server in domain mode does not advertise its teiid runtime-version
> --------------------------------------------------------------------------
>
> Key: TEIID-2650
> URL: https://issues.jboss.org/browse/TEIID-2650
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.4
> Reporter: Paul Richardson
> Assignee: Ramesh Reddy
> Priority: Blocker
> Fix For: 8.4.1, 8.5
>
>
> A standalone jboss server installed with teiid advertises its teiid runtime version at the path /subsystem=teiid/runtime-version.
> Likewise, a domain jboss server installed with teiid in the 'ha' profile should advertise its runtime version at the path /profile=ha/subsystem=teiid/runtime-version.
> However, whereas the standalone returns the correct value for this attribute, the domain mode server fails, only returning 'undefined'.
> This attribute is essential to designer in determining what version is the teiid instance. This in turns determines the functionality of the modelling that is available and which teiid client should be used for connection.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months