[JBoss JIRA] (TEIID-4265) Performance issue
by Juraj Duráni (JIRA)
Juraj Duráni created TEIID-4265:
-----------------------------------
Summary: Performance issue
Key: TEIID-4265
URL: https://issues.jboss.org/browse/TEIID-4265
Project: Teiid
Issue Type: Bug
Components: Query Engine
Reporter: Juraj Duráni
Assignee: Steven Hawkins
Attachments: dv-tpch-2.zip
I can see reduce of performance for some kind of queries (see attachment).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (TEIID-4234) Gradle blueprint
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4234?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4234:
----------------------------------
Fix Version/s: 9.1
(was: 9.0)
> Gradle blueprint
> ----------------
>
> Key: TEIID-4234
> URL: https://issues.jboss.org/browse/TEIID-4234
> Project: Teiid
> Issue Type: Feature Request
> Components: Tools
> Reporter: jay vyas
> Assignee: Steven Hawkins
> Fix For: 9.1
>
> Attachments: build.gradle
>
>
> As a app developer, I'd like to spin up a teiid/JDV application with all client-side dependencies
> without needing to use an IDE.
> Currently, most of the TEiid resources and videos are based on IDE features, bootstrapping teiid on the local machine.
> Ideally, we might host a simple Teiid server that can run in a dockerfile with sample data, along side a gradle runnable file.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (TEIID-4234) Gradle blueprint
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4234?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-4234:
-------------------------------------
Assignee: (was: Steven Hawkins)
> Gradle blueprint
> ----------------
>
> Key: TEIID-4234
> URL: https://issues.jboss.org/browse/TEIID-4234
> Project: Teiid
> Issue Type: Feature Request
> Components: Tools
> Reporter: jay vyas
> Fix For: 9.1
>
> Attachments: build.gradle
>
>
> As a app developer, I'd like to spin up a teiid/JDV application with all client-side dependencies
> without needing to use an IDE.
> Currently, most of the TEiid resources and videos are based on IDE features, bootstrapping teiid on the local machine.
> Ideally, we might host a simple Teiid server that can run in a dockerfile with sample data, along side a gradle runnable file.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (TEIID-3929) Accumulo does not return null values
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3929?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3929.
-----------------------------------
Resolution: Done
> Accumulo does not return null values
> ------------------------------------
>
> Key: TEIID-3929
> URL: https://issues.jboss.org/browse/TEIID-3929
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.3
> Reporter: Jan Stastny
> Assignee: Ramesh Reddy
> Fix For: 9.0, 8.12.5
>
>
> Accumulo doesn't return null values when a whole 'column' is being selected.
> For a command in accumulo shell like:
> {code:plain}
> scan -c name:BYTENUM
> {code}
> Accumulo returns only non-empty values, this is expected behaviour.
> Equivalent query in Teiid would be:
> {code:sql}
> SELECT ByteNum FROM SmallA
> {code}
> Which returns the same results as Accumulo does. That means, no NULL values, if there are rowids without specified column families/qualifiers missing. But when a user has his schema defined in a vdb, he probably expects, that he will get as many rows as there are in the table.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (TEIID-3929) Accumulo does not return null values
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-3929?page=com.atlassian.jira.plugin... ]
Jan Stastny commented on TEIID-3929:
------------------------------------
[~rareddy]
I checked with updated translator that I built from the upstream branch. The issue seems to be resolved by the fix.
> Accumulo does not return null values
> ------------------------------------
>
> Key: TEIID-3929
> URL: https://issues.jboss.org/browse/TEIID-3929
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.3
> Reporter: Jan Stastny
> Assignee: Ramesh Reddy
> Fix For: 9.0, 8.12.5
>
>
> Accumulo doesn't return null values when a whole 'column' is being selected.
> For a command in accumulo shell like:
> {code:plain}
> scan -c name:BYTENUM
> {code}
> Accumulo returns only non-empty values, this is expected behaviour.
> Equivalent query in Teiid would be:
> {code:sql}
> SELECT ByteNum FROM SmallA
> {code}
> Which returns the same results as Accumulo does. That means, no NULL values, if there are rowids without specified column families/qualifiers missing. But when a user has his schema defined in a vdb, he probably expects, that he will get as many rows as there are in the table.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (TEIID-3557) Can't reload VDB in domain mode
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3557?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3557.
-----------------------------------
Resolution: Done
Marking as done again as there has been no progress on reproduciblity.
> Can't reload VDB in domain mode
> -------------------------------
>
> Key: TEIID-3557
> URL: https://issues.jboss.org/browse/TEIID-3557
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.0
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Critical
> Fix For: 8.11.1, 8.12, 8.7.1.6_2
>
>
> Can't reload VDB in domain mode, get the following error:
> Server throws the following exception:
> [Server:server-one] 12:26:45,678 ERROR [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID40088 Could not replicate object org.teiid.query.tempdata.GlobalTableStoreImpl@4e6c9a30: java.lang.IllegalStateException: cluster 'ModeShape.1' is already connected to singleton transport: [dummy-1435055090515, loopback.1, ModeShape.1, loopback-dynamic.1, $TEIID_BM$, dummy-1435055090188, dummy-1435055205654, $TEIID_ED$, teiid-cache, ddl2-vdb.1]
> [Server:server-one] at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:919) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1]
> [Server:server-one] at org.jgroups.JChannel.startStack(JChannel.java:827) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1]
> [Server:server-one] at org.jgroups.JChannel._preConnect(JChannel.java:525) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1]
> [Server:server-one] at org.jgroups.JChannel.connect(JChannel.java:277) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1]
> [Server:server-one] at org.jgroups.JChannel.connect(JChannel.java:268) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1]
> [Server:server-one] at org.teiid.replication.jgroups.JGroupsObjectReplicator.replicate(JGroupsObjectReplicator.java:563) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2]
> [Server:server-one] at org.teiid.deployers.CompositeGlobalTableStore.createInstance(CompositeGlobalTableStore.java:57) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2]
> [Server:server-one] at org.teiid.jboss.VDBService$1.finishedDeployment(VDBService.java:156) [teiid-jboss-integration-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2]
> [Server:server-one] at org.teiid.deployers.VDBRepository.notifyFinished(VDBRepository.java:352) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2]
> [Server:server-one] at org.teiid.deployers.VDBRepository.finishDeployment(VDBRepository.java:308) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2]
> [Server:server-one] at org.teiid.runtime.AbstractVDBDeployer.metadataLoaded(AbstractVDBDeployer.java:202) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2]
> [Server:server-one] at org.teiid.jboss.VDBService.access$1100(VDBService.java:85) [teiid-jboss-integration-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2]
> [Server:server-one] at org.teiid.jboss.VDBService$6.run(VDBService.java:411) [teiid-jboss-integration-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2]
> [Server:server-one] at org.teiid.jboss.VDBService$7.run(VDBService.java:442) [teiid-jboss-integration-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2]
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> [Server:server-one] at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> [Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> VDB reload works fine in standalone mode.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (TEIID-4238) Remove need for quotes around cursor name declarations/fetches
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4238?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4238.
-----------------------------------
Resolution: Done
Removed the need for quoting - however mixing quoted and unquoted may be an issue as unquoted are still treated as case sensitive. We may need to change that later, but we'll have to validate what is expected.
> Remove need for quotes around cursor name declarations/fetches
> --------------------------------------------------------------
>
> Key: TEIID-4238
> URL: https://issues.jboss.org/browse/TEIID-4238
> Project: Teiid
> Issue Type: Enhancement
> Components: ODBC
> Reporter: Marc Shirley
> Assignee: Steven Hawkins
> Fix For: 9.1
>
>
> Attempting to declare a cursor without quotes results in an error similar to[1]. The quotes should be optional except in special cases, as this seems to match later standards (SQL2003). Performing fetch operations against the cursor have the same issue, where if the cursorname is not quoted, parsing errors occur.
> [1] Caused by: org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "[*]DECLARE[*] cursorname CURSOR" at line 1, column 1.
> Was expecting: "alter" | "begin" | "call" | "create" | "delete" | "drop" | "exec" | "execute" | "insert" | "merge" ...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (TEIID-4238) Remove need for quotes around cursor name declarations/fetches
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4238?page=com.atlassian.jira.plugin... ]
Work on TEIID-4238 started by Steven Hawkins.
---------------------------------------------
> Remove need for quotes around cursor name declarations/fetches
> --------------------------------------------------------------
>
> Key: TEIID-4238
> URL: https://issues.jboss.org/browse/TEIID-4238
> Project: Teiid
> Issue Type: Enhancement
> Components: ODBC
> Reporter: Marc Shirley
> Assignee: Steven Hawkins
> Fix For: 9.1
>
>
> Attempting to declare a cursor without quotes results in an error similar to[1]. The quotes should be optional except in special cases, as this seems to match later standards (SQL2003). Performing fetch operations against the cursor have the same issue, where if the cursorname is not quoted, parsing errors occur.
> [1] Caused by: org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "[*]DECLARE[*] cursorname CURSOR" at line 1, column 1.
> Was expecting: "alter" | "begin" | "call" | "create" | "delete" | "drop" | "exec" | "execute" | "insert" | "merge" ...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months