July 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3594) Change the default for command logging to write User query (start/end)

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3594?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3594: --------------------------------------- > 2) Server configuration seems appropriate, can not think of any negatives. This will also require a restart. I'll do 1 or 2. > Actually I feel like, we need to use this to control the whole command/audit logging, and remove the logging based controls like DEBUG, INFO etc. Can you elaborate on what you mean by this? > Change the default for command logging to write User query (start/end) > ---------------------------------------------------------------------- > > Key: TEIID-3594 > URL: https://issues.jboss.org/browse/TEIID-3594 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Van Halbert > Assignee: Steven Hawkins > > The command logging currently writes the user query and the source queries. Would like to have multiple levels for command logging, example: > - default, log the user query start and end entry > - debug, log the use query and the source queries -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3594) Change the default for command logging to write User query (start/end)

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3594?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3594: ------------------------------------- 1) System variable seems easy to configure than others, but require a restart of the system each time we want to toggle the behavior. 2) Server configuration seems appropriate, can not think of any negatives. 3) This seems natural as with we are logging source queries, however configuration wise this is heavy weight to define a override translator, redeploy etc. Actually I feel like, we need to use this to control the whole command/audit logging, and remove the logging based controls like DEBUG, INFO etc. > Change the default for command logging to write User query (start/end) > ---------------------------------------------------------------------- > > Key: TEIID-3594 > URL: https://issues.jboss.org/browse/TEIID-3594 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Van Halbert > Assignee: Steven Hawkins > > The command logging currently writes the user query and the source queries. Would like to have multiple levels for command logging, example: > - default, log the user query start and end entry > - debug, log the use query and the source queries -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3601) support larger row counts

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3601: ------------------------------------- Summary: support larger row counts Key: TEIID-3601 URL: https://issues.jboss.org/browse/TEIID-3601 Project: Teiid Issue Type: Feature Request Components: JDBC Driver, Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.0 In some extreme cases intermediate and final result sizes can exceed 2^31 - 1 rows. To support this we would need to make extensive changes: In the engine the tuplebuffer and logic related to indexing would need to change to long rather than int - this also touches things like join and insert processing. A new protocol version would be needed as resultmessages would need to use long rather than int indexing - however JDBC implicitly assumes int indexing such as with ResultSet.getRow. Temp table handling would need to be updated to support table sizes greater than max int. >From a processing side, although not just related row counts, we would consider increasing the parallelism of the plan. The most fundamental way to do this is to partition source queries such that more data can be read in parallel from the source. This would require extension metadata to indicate the partitioning scheme. To take full advantage of such a change the plan itself would have to be paralellized such that as much processing as possible is performed on each partition (rather than the simple case in multi-source where the data is simply unioned back together in the parent node). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3418) Allow positional group by for odbc

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3418?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3418: ------------------------------------------------ Alex Szczuczko <aszczucz(a)redhat.com> changed the Status of [bug 1227487|https://bugzilla.redhat.com/show_bug.cgi?id=1227487] from MODIFIED to ON_QA > Allow positional group by for odbc > ---------------------------------- > > Key: TEIID-3418 > URL: https://issues.jboss.org/browse/TEIID-3418 > Project: Teiid > Issue Type: Quality Risk > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.11, 8.7.4 > > > A remaining item for TEIID-3073 was that since tableau assumes we are postgresql they will use the pg specific positional group by references. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3594) Change the default for command logging to write User query (start/end)

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3594?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3594: --------------------------------------- Alternatives to control this behavior include: A system variable A server config parameter A general translator property Does anyone have a preference as to which one? > Change the default for command logging to write User query (start/end) > ---------------------------------------------------------------------- > > Key: TEIID-3594 > URL: https://issues.jboss.org/browse/TEIID-3594 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Van Halbert > Assignee: Steven Hawkins > > The command logging currently writes the user query and the source queries. Would like to have multiple levels for command logging, example: > - default, log the user query start and end entry > - debug, log the use query and the source queries -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3595) Add to audit logging the user that logs in and out

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3595?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3595: --------------------------------------- The possible events are: login attempt - an issue we have here is providing a concise set of information to the audit event. No session and potentially no VDB has been identified at this point. The alternative information set would be - vdbName, vdbVersion, authType, userName, applicationName, properties login success - we can just update the auditmessage to provide the session login fails - somewhat similar to login attempt as this could be due to an invalid vdb or auth failure logout - similar to success and can provide the session So the question would be do we do attempt/success/fail or just success/fail. And then do we heavily extend the auditmessage to accomodate login attempt/fail, create a new message type, etc. > Add to audit logging the user that logs in and out > -------------------------------------------------- > > Key: TEIID-3595 > URL: https://issues.jboss.org/browse/TEIID-3595 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Van Halbert > Assignee: Steven Hawkins > > Add the ability to write to the audit log the user that logs in and out. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3600) DB2 - error getting substring if "from position" is out of range

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3600?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3600: ---------------------------------- Issue Type: Quality Risk (was: Bug) Fix Version/s: 8.12 Component/s: Misc. Connectors > DB2 - error getting substring if "from position" is out of range > ---------------------------------------------------------------- > > Key: TEIID-3600 > URL: https://issues.jboss.org/browse/TEIID-3600 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.12 > > > If second argument of a SUBSTRING(x,y,z) function is out of range of first argument an exception is thrown [1]. Source-specific command [2]. > [1] > Caused by: com.ibm.db2.jcc.am.SqlDataException: DB2 SQL Error: SQLCODE=-138, SQLSTATE=22011, SQLERRMC=null, DRIVER=4.12.55 > at com.ibm.db2.jcc.am.hd.a(hd.java:668) > at com.ibm.db2.jcc.am.hd.a(hd.java:60) > ... > [2] > SELECT substr(varchar(g_0.TimestampValue), 40, CASE WHEN 0 > (length(varchar(g_0.TimestampValue)) - (40 - 1)) THEN (length(varchar(g_0.TimestampValue)) - (40 - 1)) ELSE 0 END) FROM SmallA AS g_0 WHERE g_0.IntKey = 1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3493) Use certificates in Salesforce SOAP API calls

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3493?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3493: ------------------------------------- Couple thoughts on it 1) Since we only need transport layer, I am thinking it only needs to use "cxf-frontend", I am not sure how much that will pull in transitively 2) With embedded Teiid direction to remove the kit altogether, I believe size should not be much of a factor. The alternative is maintain separate resource-adapters, but that seems verbose and potentially confusing to the user. > Use certificates in Salesforce SOAP API calls > --------------------------------------------- > > Key: TEIID-3493 > URL: https://issues.jboss.org/browse/TEIID-3493 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Reporter: Burak Serdar > Assignee: Steven Hawkins > Fix For: 8.12 > > > Currently salesforce connector supports user/password authentication. It would be nice if we can use certificates. > https://help.salesforce.com/apex/HTViewHelpDoc?id=security_keys_uploading... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3598) MongoDB string functions - different handling of NULL values

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3598?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3598: --------------------------------------- It would require using a case or similar expression. They seem to have a $cond that may work for that. > MongoDB string functions - different handling of NULL values > ------------------------------------------------------------ > > Key: TEIID-3598 > URL: https://issues.jboss.org/browse/TEIID-3598 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Jan Stastny > Assignee: Ramesh Reddy > > Teiid doesn't handle NULL values right in given functions when working with mongodb. > * SUBSTRING(<column resolving to NULL>,2) > ** query: > {code:sql} > SELECT INTKEY, STRINGNUM, SUBSTRING(STRINGNUM, 2) FROM BQT1.SmallA ORDER BY INTKEY > {code} > ** source query: > {code:plain} > {"$project": {{ "c_0" : "$INTKEY" , "c_1" : "$STRINGNUM" , "c_2" : { "$substr" : [ "$STRINGNUM" , { "$subtract" : [ 2 , 1]} , 4000]}}}} > {code} > ** problem: > For row with NULL value in given column returns sth like: > {code:plain}{ "_id" : ObjectId("534bf17516997a2a41000002"), "c_0" : 1, "c_1" : null, "c_2" : "" } > {code}which results in "" as result for SUBSTRING(NULL, 2) which should return NULL instead > * UCASE, LCASE (UPPER, LOWER) > ** query: > {code:sql} > SELECT intkey, stringnum, LOWER(stringnum) AS LOWER FROM BQT1.SmallA ORDER BY intkey > {code} > ** source query: > {code:plain} > {"$project": {{ "c_0" : "$INTKEY" , "c_1" : "$STRINGNUM" , "c_2" : { "$toLower" : [ "$STRINGNUM"]}}}} > {code} > ** problem: > For row with NULL value in given column returns sth like: > {code:plain} > { "_id" : ObjectId("534bf17516997a2a41000002"), "c_0" : 1, "c_1" : null, "c_2" : "" } > {code} which results in "" as result for LCASE(NULL) which should return NULL instead -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3598) MongoDB string functions - different handling of NULL values

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3598?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3598: ------------------------------------- I believe that is the behavior from MongoDB, not sure how we can prevent that. > MongoDB string functions - different handling of NULL values > ------------------------------------------------------------ > > Key: TEIID-3598 > URL: https://issues.jboss.org/browse/TEIID-3598 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Jan Stastny > Assignee: Ramesh Reddy > > Teiid doesn't handle NULL values right in given functions when working with mongodb. > * SUBSTRING(<column resolving to NULL>,2) > ** query: > {code:sql} > SELECT INTKEY, STRINGNUM, SUBSTRING(STRINGNUM, 2) FROM BQT1.SmallA ORDER BY INTKEY > {code} > ** source query: > {code:plain} > {"$project": {{ "c_0" : "$INTKEY" , "c_1" : "$STRINGNUM" , "c_2" : { "$substr" : [ "$STRINGNUM" , { "$subtract" : [ 2 , 1]} , 4000]}}}} > {code} > ** problem: > For row with NULL value in given column returns sth like: > {code:plain}{ "_id" : ObjectId("534bf17516997a2a41000002"), "c_0" : 1, "c_1" : null, "c_2" : "" } > {code}which results in "" as result for SUBSTRING(NULL, 2) which should return NULL instead > * UCASE, LCASE (UPPER, LOWER) > ** query: > {code:sql} > SELECT intkey, stringnum, LOWER(stringnum) AS LOWER FROM BQT1.SmallA ORDER BY intkey > {code} > ** source query: > {code:plain} > {"$project": {{ "c_0" : "$INTKEY" , "c_1" : "$STRINGNUM" , "c_2" : { "$toLower" : [ "$STRINGNUM"]}}}} > {code} > ** problem: > For row with NULL value in given column returns sth like: > {code:plain} > { "_id" : ObjectId("534bf17516997a2a41000002"), "c_0" : 1, "c_1" : null, "c_2" : "" } > {code} which results in "" as result for LCASE(NULL) which should return NULL instead -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2015