January 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2804) Aggregate empty filter too broad and may inappropriately filter results

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2804?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2804: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1053786|https://bugzilla.redhat.com/show_bug.cgi?id=1053786] from NEW to ASSIGNED > Aggregate empty filter too broad and may inappropriately filter results > ----------------------------------------------------------------------- > > Key: TEIID-2804 > URL: https://issues.jboss.org/browse/TEIID-2804 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.3 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7 > > > This is a regression from TEIID-2253 which consolidated logic in RulePushAggregates to handle multi-source planning. It also inappropriately expanded an empty test (which should only be applied to grouping without a group by) to some cases with group by clauses and in an attempt to broaden pushdown support utilized is not null tests. However the is not null tests are not generally valid as the aggregate could be computed against all null values for example. Depending upon this situations this could result in invalid filtering of results. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2804) Aggregate empty filter too broad and may inappropriately filter results

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2804?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2804: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1053786 > Aggregate empty filter too broad and may inappropriately filter results > ----------------------------------------------------------------------- > > Key: TEIID-2804 > URL: https://issues.jboss.org/browse/TEIID-2804 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.3 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7 > > > This is a regression from TEIID-2253 which consolidated logic in RulePushAggregates to handle multi-source planning. It also inappropriately expanded an empty test (which should only be applied to grouping without a group by) to some cases with group by clauses and in an attempt to broaden pushdown support utilized is not null tests. However the is not null tests are not generally valid as the aggregate could be computed against all null values for example. Depending upon this situations this could result in invalid filtering of results. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2785) Update ModeShape jdbc translator to return the JCR procedures in the getMetadatda() call

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2785?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2785: ------------------------------------ I vote to just change it over to a usability issue. > Update ModeShape jdbc translator to return the JCR procedures in the getMetadatda() call > ---------------------------------------------------------------------------------------- > > Key: TEIID-2785 > URL: https://issues.jboss.org/browse/TEIID-2785 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.7 > > > The ModeShapeExecutionFactory should expose the JCR procedures in the metadata when the getMetadata(..) is called. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2800) Teiid Login Issue with special characters

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2800?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2800: ---------------------------------- Fix Version/s: 8.7 Priority: Blocker (was: Major) Component/s: JDBC Driver There are two issues here. The first is that the TeiidDataSource is not properly handling encoded properties. The next and more severe issue is that getConnection(user, password) is not conveying the arguments and instead just using the credentials on the data source. > Teiid Login Issue with special characters > ----------------------------------------- > > Key: TEIID-2800 > URL: https://issues.jboss.org/browse/TEIID-2800 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 8.1 > Environment: Mainframe Jboss 7.1.1 > Reporter: Gautam Banerjee > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.7 > > > When we try to login to teiid programmatically through datasource, we are having problem with username having special characters. > We are encoding the special character as per url encoding > eg : username %xyz is encoded as %25xyz but teiid does not decode the special character while passing username. So the username passed by teiid is %25xyz which fails authentication as the actual username is %xyz -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2800) Teiid Login Issue with special characters

by Gautam Banerjee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2800?page=com.atlassian.jira.plugin... ] Gautam Banerjee commented on TEIID-2800: ---------------------------------------- This URL is got by debugging. We are not directly setting the URL. We instantiate TeiidDataSource and get the Connection passing userid and password. The other parameters set on teiidDataSource directly. TeiidDataSource teiidDataSource = new TeiidDataSource(); teiidDataSource.getConnection("user", "password"); > Teiid Login Issue with special characters > ----------------------------------------- > > Key: TEIID-2800 > URL: https://issues.jboss.org/browse/TEIID-2800 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.1 > Environment: Mainframe Jboss 7.1.1 > Reporter: Gautam Banerjee > Assignee: Steven Hawkins > > When we try to login to teiid programmatically through datasource, we are having problem with username having special characters. > We are encoding the special character as per url encoding > eg : username %xyz is encoded as %25xyz but teiid does not decode the special character while passing username. So the username passed by teiid is %25xyz which fails authentication as the actual username is %xyz -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2785) Update ModeShape jdbc translator to return the JCR procedures in the getMetadatda() call

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2785?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2785: --------------------------------------- So I would either change this over to a general Designer/Teiid pushdown function usability issue or close it out and start another one to that effect. > Update ModeShape jdbc translator to return the JCR procedures in the getMetadatda() call > ---------------------------------------------------------------------------------------- > > Key: TEIID-2785 > URL: https://issues.jboss.org/browse/TEIID-2785 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.7 > > > The ModeShapeExecutionFactory should expose the JCR procedures in the metadata when the getMetadata(..) is called. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2805) Fix Accumulo module missing dependencies

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2805?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-2805: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Fix Accumulo module missing dependencies > ---------------------------------------- > > Key: TEIID-2805 > URL: https://issues.jboss.org/browse/TEIID-2805 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 8.7 > Reporter: Tom Arnold > Assignee: Ramesh Reddy > Priority: Minor > > 08:04:01,070 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50029 VDB accum.1 model "accumModel" metadata is currently being loaded. Start Time: 1/15/14 8:04 AM > 08:04:01,170 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (teiid-async-threads - 1) IJ000604: Throwable while attempting to get a new connection: null: java.lang.NoClassDefFoundError: org/apache/commons/io/output/ByteArrayOutputStream > at org.apache.accumulo.core.client.ZooKeeperInstance.getConnector(ZooKeeperInstance.java:222) > See forum thread for more details. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2805) Fix Accumulo module missing dependencies

by Tom Arnold (JIRA)

Tom Arnold created TEIID-2805: --------------------------------- Summary: Fix Accumulo module missing dependencies Key: TEIID-2805 URL: https://issues.jboss.org/browse/TEIID-2805 Project: Teiid Issue Type: Bug Components: Build/Kits Affects Versions: 8.7 Reporter: Tom Arnold Assignee: Steven Hawkins Priority: Minor 08:04:01,070 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50029 VDB accum.1 model "accumModel" metadata is currently being loaded. Start Time: 1/15/14 8:04 AM 08:04:01,170 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (teiid-async-threads - 1) IJ000604: Throwable while attempting to get a new connection: null: java.lang.NoClassDefFoundError: org/apache/commons/io/output/ByteArrayOutputStream at org.apache.accumulo.core.client.ZooKeeperInstance.getConnector(ZooKeeperInstance.java:222) See forum thread for more details. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2785) Update ModeShape jdbc translator to return the JCR procedures in the getMetadatda() call

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2785?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2785: --------------------------------------- > If the push down functions are being injected into the metadata, can they also be exposed in the DDL when getSchema is called? That's what I mean by "For design time we have a couple of options, the simpliest of which is to add an import option to include the pushdown functions in the schema metadata (although it would be nice if the resolver knew the relationship between the function definitions)" If they are on the schema as well the resolver will currently allow that - see the resolution to TEIID-2794. But it would be nice through an extension or other metadata to ensure that the functions do represent the same thing. > Update ModeShape jdbc translator to return the JCR procedures in the getMetadatda() call > ---------------------------------------------------------------------------------------- > > Key: TEIID-2785 > URL: https://issues.jboss.org/browse/TEIID-2785 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.7 > > > The ModeShapeExecutionFactory should expose the JCR procedures in the metadata when the getMetadata(..) is called. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2785) Update ModeShape jdbc translator to return the JCR procedures in the getMetadatda() call

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2785?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2785: ------------------------------------ If the push down functions are being injected into the metadata, can they also be exposed in the DDL when getSchema is called? > Update ModeShape jdbc translator to return the JCR procedures in the getMetadatda() call > ---------------------------------------------------------------------------------------- > > Key: TEIID-2785 > URL: https://issues.jboss.org/browse/TEIID-2785 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.7 > > > The ModeShapeExecutionFactory should expose the JCR procedures in the metadata when the getMetadata(..) is called. -- 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

10 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2014