[JBoss JIRA] (TEIID-2410) issues with output buffer blocking
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/TEIID-2410?page=com.atlassian.jira.plugin... ]
Johnathon Lee updated TEIID-2410:
---------------------------------
Fix Version/s: 7.7.6
> issues with output buffer blocking
> ----------------------------------
>
> Key: TEIID-2410
> URL: https://issues.jboss.org/browse/TEIID-2410
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.3, 7.7.6
>
>
> when a local connection (regardless of using the calling thread) blocks on the output buffer (which cannot happen with forward only and using the calling thread, but due to another issue can occur with a scroll insensitive result) no corresponding process thread is awakened to process pending work.
> Output blocking should also be disabled for non-forward only results. This was disabled at some point by a refactoring to reuse the output buffer from the plan.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (TEIID-2366) If where clause contains both equal and greater then conditions then query may return no results
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/TEIID-2366?page=com.atlassian.jira.plugin... ]
Johnathon Lee updated TEIID-2366:
---------------------------------
Fix Version/s: 7.7.6
(was: 7.7.5)
> If where clause contains both equal and greater then conditions then query may return no results
> ------------------------------------------------------------------------------------------------
>
> Key: TEIID-2366
> URL: https://issues.jboss.org/browse/TEIID-2366
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.4
> Reporter: Paul Lysak
> Assignee: Steven Hawkins
> Labels: query,, where
> Fix For: 8.3, 7.7.6
>
>
> If WHERE clause contains '>' and '=' conditions for the same field then query may produce no result - depending on conditions order.
> The problem seems to be in org.teiid.query.rewriter.QueryRewriter class, method rewriteAndConjunct(). Pay attention to following piece of code:
> ... if (cc1.getOperator() == CompareCriteria.EQ) {
> if (!Evaluator.compare(cc1, ((Constant)cc1.getRightExpression()).getValue(), ((Constant)cc.getRightExpression()).getValue())) {
> return FALSE_CRITERIA;
> }
> Note that cc1 (which is guaranteed to have EQ criterion) is passed to Evaluator.compare. Thus right expressions of cc and cc1 are required to be equal. But if we have one contition EQ and another GT then it should instead check if right side of EQ is bigger then right side of GT.
> Bug TEIID-1704 describes a bit similar situation but it is still a different case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (TEIID-2352) START USER COMMAND and END USER COMMAND are not shown with loglevel=DEBUG
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/TEIID-2352?page=com.atlassian.jira.plugin... ]
Johnathon Lee updated TEIID-2352:
---------------------------------
Fix Version/s: 7.7.6
> START USER COMMAND and END USER COMMAND are not shown with loglevel=DEBUG
> -------------------------------------------------------------------------
>
> Key: TEIID-2352
> URL: https://issues.jboss.org/browse/TEIID-2352
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 7.7.1
> Reporter: Hisanobu Okuda
> Assignee: Steven Hawkins
> Fix For: 8.3, 7.7.6
>
>
> With loglevel=DEBUG, START USER COMMAND and END USER COMMAND log messages are not shown.
> With loglevel=TRACE, they are shown:-
> {code}
> 2013-01-17 13:45:58,205 DEBUG [org.teiid.COMMAND_LOG] (New I/O server worker #1-1:) START USER COMMAND:startTime=2013-01-17 13:45:58.205 requestID=GQ2RlqzuDfet.0 txID=null sessionID=GQ2RlqzuDfet applicationName=JDBC principal=user@teiid-security vdbName=PREVIEW_31af68bd-5f4d-4e77-b13c-94823d02dcf8_test_project vdbVersion=1 sql=select * from "v2"."data2View"
> ...
> 2013-01-17 13:50:23,968 DEBUG [org.teiid.COMMAND_LOG] (Worker2_QueryProcessorQueue9:) END USER COMMAND: endTime=2013-01-17 13:50:23.968 requestID=GQ2RlqzuDfet.0 txID=null sessionID=GQ2RlqzuDfet principal=user@teiid-security vdbName=PREVIEW_31af68bd-5f4d-4e77-b13c-94823d02dcf8_test_project vdbV
> ersion=1 finalRowCount=2
> {code}
> But shown as "DEBUG".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (TEIID-2417) Allow translator properties to be overridable
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2417:
-------------------------------------
Summary: Allow translator properties to be overridable
Key: TEIID-2417
URL: https://issues.jboss.org/browse/TEIID-2417
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 7.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.3
If an ExecutionFactory subclass attempts to override a parent translator property the parent property will be used instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (TEIID-2402) Enable session context be available in the all log messages
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2402?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2402:
---------------------------------------
I've made the session id and vdb name/version available in the MDC as teiid-session and teiid-vdb respectively. To use those values the logging extension would have to access org.jboss.logging.MDC or a standard logger could use a format pattern that included the mdc keys - i.e. %X{teiid-session} - see also https://community.jboss.org/thread/161799
A caveat is that this will not currently work with the Java logger (used for embedded) as Java logging lacks an mdc concept. We could enable the functionality by leveraging JBoss logging in embedded or by rolling our own support.
Does this seem sufficient or should we add the user name as well?
> Enable session context be available in the all log messages
> -----------------------------------------------------------
>
> Key: TEIID-2402
> URL: https://issues.jboss.org/browse/TEIID-2402
> Project: Teiid
> Issue Type: Enhancement
> Components: Common
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 8.3
>
>
> Inject work context into all the Teiid based messages such that a custom logger can be written to filter based on logged in user, vdb
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months