March 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2385) Add VDB Deployment Logic for RHQ Plugin

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIID-2385?page=com.atlassian.jira.plugin... ] Ted Jones updated TEIID-2385: ----------------------------- Git Pull Request: https://github.com/teiid/teiid-rhq/pull/3 > Add VDB Deployment Logic for RHQ Plugin > --------------------------------------- > > Key: TEIID-2385 > URL: https://issues.jboss.org/browse/TEIID-2385 > Project: Teiid > Issue Type: Feature Request > Components: RHQ > Affects Versions: 8.3 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.3 > > > The content tab of a deployable resource in RHQ allows for deployment and versioning of resources. We need to add this to the Teiid RHQ plugin. -- 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

1
0
0 / 0

[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 resolved TEIID-2402. ----------------------------------- Resolution: Done Marking the session object available to all log messages doesn't seem necessary. Also jboss views the use of the mdc for potentially mutable objects as an anti-pattern and forces the values to string. Any other approach such as the manipulation of the log record parameters seems like a just a hack, so the approach here is to just put the session in and vdb name/version strings in the mdc. The docs have been updated to describe the mdc properties and the standalone.xml was updated to include the session in all of the messages (although this is redundant in some messages). The customized logger may use the admin api if needed to get the session based upon the session id. Beyond this if someone absolutely needs additional context information in the logging layer from the same thread as the caller, then the approach should be to reference the DQPWorkContext - but that should be considered an unsupported use of an internal api. > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2419) minor message improvements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2419?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2419. ----------------------------------- Resolution: Done made the updates from the description. > minor message improvements > -------------------------- > > Key: TEIID-2419 > URL: https://issues.jboss.org/browse/TEIID-2419 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.3 > > > The vdbmetadatamapper expects message values to be non-null, so we need to make sure that a values is set. Also the log for an invalid session on terminate should be at a detail level and not at a warning level as this can naturally occur and there is already a log of the attempt. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2285) Enhance Loopback Translator to retrieve custom data

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2285?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2285: --------------------------------------- No, that is only to set the default behavior of all capabilities, which is the TeiidExecutionFactory. Otherwise the delegate will be set at runtime via injection. > Enhance Loopback Translator to retrieve custom data > --------------------------------------------------- > > Key: TEIID-2285 > URL: https://issues.jboss.org/browse/TEIID-2285 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.2 > Reporter: Filip Nguyen > Assignee: Filip Nguyen > Priority: Minor > Fix For: 8.3 > > > Loopback Translator was identified as suitable way of testing Teiid engine performance. It would be nice if the Translator would mimic database behavior better in some aspects: > * Possibility to define what data will be retrieved in the columns > * Possibility of Unique data in column to mimic database generator -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2285) Enhance Loopback Translator to retrieve custom data

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2285?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2285: ------------------------------------- Does it need dependencies added to all the other translators in the its module.xml file, so that it can delegate correctly? > Enhance Loopback Translator to retrieve custom data > --------------------------------------------------- > > Key: TEIID-2285 > URL: https://issues.jboss.org/browse/TEIID-2285 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.2 > Reporter: Filip Nguyen > Assignee: Filip Nguyen > Priority: Minor > Fix For: 8.3 > > > Loopback Translator was identified as suitable way of testing Teiid engine performance. It would be nice if the Translator would mimic database behavior better in some aspects: > * Possibility to define what data will be retrieved in the columns > * Possibility of Unique data in column to mimic database generator -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2417) Allow translator properties to be overridable

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2417?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2417. ----------------------------------- Resolution: Done Modified the translatorutil to consult subclasses first and to handle method overrides by name. > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2419) minor message improvements

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2419: ------------------------------------- Summary: minor message improvements Key: TEIID-2419 URL: https://issues.jboss.org/browse/TEIID-2419 Project: Teiid Issue Type: Quality Risk Components: Server Affects Versions: 8.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.3 The vdbmetadatamapper expects message values to be non-null, so we need to make sure that a values is set. Also the log for an invalid session on terminate should be at a detail level and not at a warning level as this can naturally occur and there is already a log of the attempt. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2363) proactive buffering not occurring for the inner side of an outer join on "MERGE JOIN (SORT/ALREADY_SORTED)"

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2363?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2363: --------------------------------- Fix Version/s: 7.7.6 > proactive buffering not occurring for the inner side of an outer join on "MERGE JOIN (SORT/ALREADY_SORTED)" > ----------------------------------------------------------------------------------------------------------- > > Key: TEIID-2363 > URL: https://issues.jboss.org/browse/TEIID-2363 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.7.2 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 8.3, 7.7.6 > > > The issue here is this is an outer join and the inner side (the already sorted side) will be buffered regardless. Current logic does not catch blocked exceptions from one side and pro-actively buffer the other - rather we are serially performing the sort and then continue with the loading of the inner side > For inner joins there is a clear trade-off between execution speed and buffering so this behavior may have to be hint or config driven for non-dependent non-outer joins. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2392) Pushdown common table query invalid

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2392?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2392: --------------------------------- Fix Version/s: 7.7.6 > Pushdown common table query invalid > ----------------------------------- > > Key: TEIID-2392 > URL: https://issues.jboss.org/browse/TEIID-2392 > 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 > > > If a common table expression that can produce a query that contains different column names than either the assumed or explicit names in the with clause, then the pushed query can contain invalid column references. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2383) InputStreamReader throws MalformedInputException when handling multi-byte characters

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2383?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2383: --------------------------------- Fix Version/s: 7.7.6 > InputStreamReader throws MalformedInputException when handling multi-byte characters > ------------------------------------------------------------------------------------ > > Key: TEIID-2383 > URL: https://issues.jboss.org/browse/TEIID-2383 > Project: Teiid > Issue Type: Bug > Components: Common > Affects Versions: 7.7.1 > Reporter: Hisanobu Okuda > Assignee: Steven Hawkins > Fix For: 8.3, 7.7.6 > > Attachments: sample.zip, simple_client.tar > > > My VDB uses File translator to handle a csv file which contains multi-byte characters. Reading some csv file via the VDB, MalformedInputException always occurs. -- 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

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2013