[JBoss JIRA] (TEIID-3204) Admin shell throws an IncompatibleClassChangeError
by Juraj Duráni (JIRA)
Juraj Duráni created TEIID-3204:
-----------------------------------
Summary: Admin shell throws an IncompatibleClassChangeError
Key: TEIID-3204
URL: https://issues.jboss.org/browse/TEIID-3204
Project: Teiid
Issue Type: Bug
Affects Versions: 8.7.1
Environment: OS: fedora 20
arch: x86_64
java: oracle 1.7
Reporter: Juraj Duráni
Assignee: Steven Hawkins
Admin shell throws an IncompatibleClassChangeError when wrong path to groovy script is provided along with load command.
Actual result:
===> [import static org.teiid.adminshell.AdminShell.*; import static org.teiid.adminshell.GroovySqlExtensions.*; import org.teiid.adminapi.*;]
FATAL: java.lang.IncompatibleClassChangeError: the number of constructors during runtime and compile time for java.lang.Exception do not match. Expected 4 but got 5
java.lang.IncompatibleClassChangeError: the number of constructors during runtime and compile time for java.lang.Exception do not match. Expected 4 but got 5
at groovy.lang.MetaClassImpl.selectConstructorAndTransformArguments(MetaClassImpl.java:1406)
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.selectConstructorAndTransformArguments(ScriptBytecodeAdapter.java:237)
at org.codehaus.groovy.tools.shell.CommandException.<init>(Command.groovy:60)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
....
....
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (TEIID-587) Better pushdown support for exotic joins
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-587?page=com.atlassian.jira.plugin.... ]
Steven Hawkins updated TEIID-587:
---------------------------------
Assignee: (was: Steven Hawkins)
> Better pushdown support for exotic joins
> ----------------------------------------
>
> Key: TEIID-587
> URL: https://issues.jboss.org/browse/TEIID-587
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 6.1.0
> Reporter: Steven Hawkins
> Fix For: 9.0
>
>
> Our optimizations get in the way of Salesforce pushdown. Specifically rewriting like when possible to = and converting outer joins to inner joins. In both cases we would need to not perform the optimization in the first place or convert into an acceptable form prior to pushdown.
> The next is that salesforce, while requiring key criteria also allows other criteria in the left outer join on clause (which would be the same as having criteria on the nested relationship query in the salesforce query). With the capabilities as currently defined this would cause the query to not be pushed down. We should consider adding a relational supported join criteria type that requires key criteria but allows for outside criteria. Also we should treat the lack of inner join support to mean that criteria on the inner side of an outer join cannot be pushed.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (TEIID-2416) Create a JDBC driver SDK
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2416?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2416:
----------------------------------
Assignee: (was: Steven Hawkins)
> Create a JDBC driver SDK
> ------------------------
>
> Key: TEIID-2416
> URL: https://issues.jboss.org/browse/TEIID-2416
> Project: Teiid
> Issue Type: Feature Request
> Components: Connector API, Query Engine
> Reporter: Steven Hawkins
>
> We should promote an offering of Teiid as just a JDBC toolkit via translator development with an emphasis on a minimal footprint (starting with Embedded, but possibly allowing for the exclusion of large dependencies - primarily saxon, but also xom, nux, etc.).
> More than likely a simplistic configuration scenario via the TeiidDataSource/TeiidDriver would be offered.
> There would be a well-documented and straight-forward migration path to full server deployment as well.
> We should also put more thought into the pass-through sql scenario for additional flexibility in issuing queries.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (TEIID-1131) Document/expand sequence support
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1131?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-1131:
----------------------------------
Assignee: (was: Steven Hawkins)
> Document/expand sequence support
> --------------------------------
>
> Key: TEIID-1131
> URL: https://issues.jboss.org/browse/TEIID-1131
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Connector, Query Engine
> Affects Versions: 7.0
> Reporter: Steven Hawkins
>
> Currently sequence workaround logic only exists for oracle and is undocumented. We should look at expanding sequence support - even for dynamic vdbs, see SQuriel's handling of system queries for retrieving sequence metadata.
> At least allowing the workaround logic to work for all sources that support sequences (Postgres, DB2, etc.) would be good.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months