April 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2920) Certain Translator Override Definitions for JDBC have identical display names

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2920?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-2920: ----------------------------------- Assignee: Ramesh Reddy > Certain Translator Override Definitions for JDBC have identical display names > ----------------------------------------------------------------------------- > > Key: TEIID-2920 > URL: https://issues.jboss.org/browse/TEIID-2920 > Project: Teiid > Issue Type: Bug > Reporter: Barry LaFond > Assignee: Ramesh Reddy > > In VDB editor, noticed that their are duplicate display names for certain JDBC translator properties. Confusing... > Debugged a little and here are the culprits I found: > ID = supportsDirectQueryProcedure > * Display Name = *Supports direct query procedure* > ID = supportsNativeQueries > * Display Name = *Supports direct query procedure* > ID = DirectQueryProcedureName > * Display Name = *Name of the direct query procedure* > ID = NativeQueryProcedureName > * Display Name = *Name of the direct query procedure* -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2920) Certain Translator Override Definitions for JDBC have identical display names

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2920?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2920: -------------------------------- Fix Version/s: 8.7 > Certain Translator Override Definitions for JDBC have identical display names > ----------------------------------------------------------------------------- > > Key: TEIID-2920 > URL: https://issues.jboss.org/browse/TEIID-2920 > Project: Teiid > Issue Type: Bug > Reporter: Barry LaFond > Assignee: Ramesh Reddy > Fix For: 8.7 > > > In VDB editor, noticed that their are duplicate display names for certain JDBC translator properties. Confusing... > Debugged a little and here are the culprits I found: > ID = supportsDirectQueryProcedure > * Display Name = *Supports direct query procedure* > ID = supportsNativeQueries > * Display Name = *Supports direct query procedure* > ID = DirectQueryProcedureName > * Display Name = *Name of the direct query procedure* > ID = NativeQueryProcedureName > * Display Name = *Name of the direct query procedure* -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2920) Certain Translator Override Definitions for JDBC have identical display names

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIID-2920?page=com.atlassian.jira.plugin... ] Barry LaFond moved TEIIDDES-2105 to TEIID-2920: ----------------------------------------------- Project: Teiid (was: Teiid Designer) Key: TEIID-2920 (was: TEIIDDES-2105) > Certain Translator Override Definitions for JDBC have identical display names > ----------------------------------------------------------------------------- > > Key: TEIID-2920 > URL: https://issues.jboss.org/browse/TEIID-2920 > Project: Teiid > Issue Type: Bug > Reporter: Barry LaFond > > In VDB editor, noticed that their are duplicate display names for certain JDBC translator properties. Confusing... > Debugged a little and here are the culprits I found: > ID = supportsDirectQueryProcedure > * Display Name = *Supports direct query procedure* > ID = supportsNativeQueries > * Display Name = *Supports direct query procedure* > ID = DirectQueryProcedureName > * Display Name = *Name of the direct query procedure* > ID = NativeQueryProcedureName > * Display Name = *Name of the direct query procedure* -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2914) Infinispan Connector didn't have the advanced searching option exposed

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2914?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2914: ------------------------------------ I'll remove the resource-adapter property and undo what was added. Then create a translator that reads the metadata from the protobuf and add the query logic that performs the DSL searching. > Infinispan Connector didn't have the advanced searching option exposed > ---------------------------------------------------------------------- > > Key: TEIID-2914 > URL: https://issues.jboss.org/browse/TEIID-2914 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7, 8.7.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > > The advanced searching option (i.e, lucene searching) that is defined in the .rar was not being picked up in the connector. > Also, it was incorrectly defined on the translator, because the translator cannot override how the cache is configured. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2914) Infinispan Connector didn't have the advanced searching option exposed

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2914?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2914: --------------------------------------- Van any additional thoughts on the above? > Infinispan Connector didn't have the advanced searching option exposed > ---------------------------------------------------------------------- > > Key: TEIID-2914 > URL: https://issues.jboss.org/browse/TEIID-2914 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7, 8.7.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > > The advanced searching option (i.e, lucene searching) that is defined in the .rar was not being picked up in the connector. > Also, it was incorrectly defined on the translator, because the translator cannot override how the cache is configured. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2896) Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2896?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2896: --------------------------------------- Confirmed the sample works with the changes. > Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length > --------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2896 > URL: https://issues.jboss.org/browse/TEIID-2896 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.7 > > Attachments: sample, TEIID-2896.patch > > > Current behavior is that data lines too short to fit a fixed width data interpretation produces an error such as "Error: Text parse error: Fixed width line width 35 is smaller than the expected 60 on text line 1 in file:/tmp/file.csv.". The customer's use case is interpreting data files from another application which bundles multiple types of data along with additional descriptive info/metadata about the data contained within the file. As the error is thrown if any lines after the first interpreted line are shorter than the summed value of the fixed width columns, they are unable to query the file. The customer wishes for the ERROR to be suppressed and the query to return the data independent of whether it fits the fixed width criteria and potentially to be able to filter the data being retrieved. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2918) function invocation failure message refinement

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2918?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2918. ----------------------------------- Fix Version/s: 8.7 Resolution: Done Removed the underlying message from the exception. We should come up with a more general way of doing this (for example the server when a query exception is logged in RequestWorkItem). Otherwise when the message isn't reported there's a "root null" or most of the time that it is the exception becomes quite verbose. > function invocation failure message refinement > ---------------------------------------------- > > Key: TEIID-2918 > URL: https://issues.jboss.org/browse/TEIID-2918 > Project: Teiid > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7 > > > TEIID-2584 modified the function invocation exception message, but the invocationtargetexception was used, which does not produce a message. > The server side already attempts to display the root exception with when an exception is logged, so this kind of logic is only needed for the client exception - which we could treat in a similar way to produce a more verbose exception. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2919) BigInteger and BigDecimal datatypes are converted into string in MongoDB translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2919?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2919: ------------------------------------- I do not think Mongo has big decimal type, need to see what are the alternatives > BigInteger and BigDecimal datatypes are converted into string in MongoDB translator > ------------------------------------------------------------------------------------- > > Key: TEIID-2919 > URL: https://issues.jboss.org/browse/TEIID-2919 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Filip Elias > Assignee: Ramesh Reddy > Fix For: 8.7.1 > > > Description of problem: > BigInteger and BigDecimal datatypes are converted into string in MongoDB translator (MongoDBExecutionFactory.java). User can't use these datatypes in the WHERE clause. > For example > The query: > > SELECT IntKey FROM SmallA where BIGINTEGERVALUE > 1 > returns no results because BIGINTEGERVALUE > 1 is converted into > { "BIGINTEGERVALUE" : { "$gt" : "1"}} > but is should be > { "BIGINTEGERVALUE" : { "$gt" : 1}} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2919) BigInteger and BigDecimal datatypes are converted into string in MongoDB translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2919?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-2919: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > BigInteger and BigDecimal datatypes are converted into string in MongoDB translator > ------------------------------------------------------------------------------------- > > Key: TEIID-2919 > URL: https://issues.jboss.org/browse/TEIID-2919 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Filip Elias > Assignee: Ramesh Reddy > Fix For: 8.7.1 > > > Description of problem: > BigInteger and BigDecimal datatypes are converted into string in MongoDB translator (MongoDBExecutionFactory.java). User can't use these datatypes in the WHERE clause. > For example > The query: > > SELECT IntKey FROM SmallA where BIGINTEGERVALUE > 1 > returns no results because BIGINTEGERVALUE > 1 is converted into > { "BIGINTEGERVALUE" : { "$gt" : "1"}} > but is should be > { "BIGINTEGERVALUE" : { "$gt" : 1}} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2919) BigInteger and BigDecimal datatypes are converted into string in MongoDB translator

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2919?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2919: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1084373 > BigInteger and BigDecimal datatypes are converted into string in MongoDB translator > ------------------------------------------------------------------------------------- > > Key: TEIID-2919 > URL: https://issues.jboss.org/browse/TEIID-2919 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Filip Elias > Assignee: Steven Hawkins > Fix For: 8.7.1 > > > Description of problem: > BigInteger and BigDecimal datatypes are converted into string in MongoDB translator (MongoDBExecutionFactory.java). User can't use these datatypes in the WHERE clause. > For example > The query: > > SELECT IntKey FROM SmallA where BIGINTEGERVALUE > 1 > returns no results because BIGINTEGERVALUE > 1 is converted into > { "BIGINTEGERVALUE" : { "$gt" : "1"}} > but is should be > { "BIGINTEGERVALUE" : { "$gt" : 1}} -- 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, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2014