[JBoss JIRA] (TEIID-4938) CLI getVDB operation domain mode - result of the operation is not in "result" element
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4938?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4938.
-----------------------------------
Resolution: Rejected
> Or, are you saying that this is done by WildFly and you cannot affect it?
Yes, that is correct.
The admin api does create a consolidated output for many operations - but some of that only works correctly after the fixes mentioned above.
> CLI getVDB operation domain mode - result of the operation is not in "result" element
> -------------------------------------------------------------------------------------
>
> Key: TEIID-4938
> URL: https://issues.jboss.org/browse/TEIID-4938
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 9.3, 8.12.10.6_3
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Priority: Minor
>
> If user reads status of VDB in domain mode, result of the operation is not written in the "result" attribute, but in separate attribute. Executing same operation in standalone mode, result is in "result" element.
> {code:plain|title=Domain mode result}
> [domain@localhost:9990 /] /profile=full/subsystem=teiid:get-vdb(...)
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => {"main-server-group" => {"host" => {"master" => {
> "server-one" => {"response" => {
> "outcome" => "success",
> "result" => {...
> }
> }},
> "server-two" => {"response" => {
> "outcome" => "success",
> "result" => {...
> }
> }}
> }}}}
> }
> {code}
> {code:plain|title=Standalone mode result}
> [standalone@localhost:9990 /] /subsystem=teiid:get-vdb(...)
> {
> "outcome" => "success",
> "result" => {...
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (TEIID-4942) Statement batch does not enforce autoCommitTxn
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-4942:
-------------------------------------
Summary: Statement batch does not enforce autoCommitTxn
Key: TEIID-4942
URL: https://issues.jboss.org/browse/TEIID-4942
Project: Teiid
Issue Type: Bug
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.0
Using Statement.executeBatch will not start a wrapping transaction for the entire batch - which is expected, but it also will not start transactions at the statement level - which is not expected.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (TEIID-4941) [RFE] Display a more informative error message when a query takes too long and times out
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4941?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4941:
----------------------------------
Issue Type: Enhancement (was: Feature Request)
Fix Version/s: 10.0
Yes, in most circumstances we should be able to expand upon this message.
> [RFE] Display a more informative error message when a query takes too long and times out
> ----------------------------------------------------------------------------------------
>
> Key: TEIID-4941
> URL: https://issues.jboss.org/browse/TEIID-4941
> Project: Teiid
> Issue Type: Enhancement
> Affects Versions: 8.8
> Reporter: Yuming Zhu
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: 10.0
>
>
> This issue is from our user of RedHat internal pnt-devops Teiid.
> Reality
> {code:java}$ echo "SOME COMPLICATED QUERY" | psql -h virtualdb.engineering.redhat.com -p 5433 -d public
> ERROR: 57014 TEIID30160 The request AXhWh34gdzbY.0 has been cancelled.
> DETAIL: org.teiid.jdbc.TeiidSQLException: 57014 TEIID30160 The request AXhWh34gdzbY.0 has been cancelled.
> {code}
> Expected
> {code:java}$ echo "SOME COMPLICATED QUERY" | psql -h virtualdb.engineering.redhat.com -p 5433 -d public
> The request AXhWh34gdzbY.0 has been cancelled. The query takes too long/timed out/whatever/resources exhausted
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (TEIID-4939) Enhance translator auto-detect and ddl deployment
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4939?page=com.atlassian.jira.plugin... ]
Kylin Soong updated TEIID-4939:
-------------------------------
Fix Version/s: 10.0
> Enhance translator auto-detect and ddl deployment
> --------------------------------------------------
>
> Key: TEIID-4939
> URL: https://issues.jboss.org/browse/TEIID-4939
> Project: Teiid
> Issue Type: Sub-task
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 10.0
>
>
> The current translator auto-detect logic: If the translators not configured manually, all class path translator be initialize and started, this enhancement for add a check for translator mapped driver classes or mcf class exist then initialize and start.
> The current ddl deployment only support use configuration way not support via main method parameter, this enhancement add for this.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years