October 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3169) Update infinispan-cache translator to use DSLQuery in library mode

by Van Halbert (JIRA)

Van Halbert created TEIID-3169: ---------------------------------- Summary: Update infinispan-cache translator to use DSLQuery in library mode Key: TEIID-3169 URL: https://issues.jboss.org/browse/TEIID-3169 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Affects Versions: 8.7.1 Reporter: Van Halbert Assignee: Steven Hawkins The curent lucene query logic needs to be upgraded to use the DSL query logic to perform searches on the cache when in library mode. This logic is currently being used in the infinispan-cache-dsl translator. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3169) Update infinispan-cache translator to use DSLQuery in library mode

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3169?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-3169: ---------------------------------- Assignee: Van Halbert (was: Steven Hawkins) > Update infinispan-cache translator to use DSLQuery in library mode > ------------------------------------------------------------------ > > Key: TEIID-3169 > URL: https://issues.jboss.org/browse/TEIID-3169 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Van Halbert > > The curent lucene query logic needs to be upgraded to use the DSL query logic to perform searches on the cache when in library mode. This logic is currently being used in the infinispan-cache-dsl translator. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3168) SQL Server requires N prefix for unicode literals

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3168?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3168. ----------------------------------- Resolution: Done Switched the sybase/sqlserver logic to look for non-ascii chars and use the N literal prefix. > SQL Server requires N prefix for unicode literals > ------------------------------------------------- > > Key: TEIID-3168 > URL: https://issues.jboss.org/browse/TEIID-3168 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > > SQL Server requires the use of the N prefix for string literals when there are non-ascii/windows characters present. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3168) SQL Server requires N prefix for unicode literals

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3168: ------------------------------------- Summary: SQL Server requires N prefix for unicode literals Key: TEIID-3168 URL: https://issues.jboss.org/browse/TEIID-3168 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7.1, 8.9 SQL Server requires the use of the N prefix for string literals when there are non-ascii/windows characters present. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3166) Allow allowDiskUse setting in MongoDB translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3166?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3166: --------------------------------------- Is there a downside to always including this hint such that it could be driven by a translator property? Or should it be driven off of a source specific hint? > Allow allowDiskUse setting in MongoDB translator > ------------------------------------------------ > > Key: TEIID-3166 > URL: https://issues.jboss.org/browse/TEIID-3166 > Project: Teiid > Issue Type: Enhancement > Reporter: Harrison Gentry > Assignee: Ramesh Reddy > Priority: Minor > > When querying a MongoDB, steps of computation are limited to 100MiB. Querying large databases can easily exceed this limit, so usually allowDiskUse:true is passed in the aggregate query: > http://docs.mongodb.org/manual/reference/command/aggregate/ > In Teiid, however, there is currently no way to specify this with SQL. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2813) Report translator CPU time

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2813?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2813: ---------------------------------- Fix Version/s: 8.10 Component/s: Query Engine Moving into 8.10 for TEIID-3146 > Report translator CPU time > -------------------------- > > Key: TEIID-2813 > URL: https://issues.jboss.org/browse/TEIID-2813 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Mark Addleman > Assignee: Steven Hawkins > Fix For: 8.10 > > > The COMMAND_LOG ought to report the CPU time accumulated by the translator for performance tuning purposes. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3167) Enhance TEXTTABLE to support TRIM as a configurable option for Delimited Text Files

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3167?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3167: ---------------------------------- Fix Version/s: 8.10 Component/s: Query Engine To clarify non-qualified entries are fully trimmed, and whitespace outside of qualified entries is trimmed for delimited files. The change here would be to not trim non-qualified entries. > Enhance TEXTTABLE to support TRIM as a configurable option for Delimited Text Files > ----------------------------------------------------------------------------------- > > Key: TEIID-3167 > URL: https://issues.jboss.org/browse/TEIID-3167 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Environment: Teiid 8.8.0 Final > Reporter: Shiveeta Mattoo > Assignee: Steven Hawkins > Labels: File-connector, TEXTTABLE, TRIM > Fix For: 8.10 > > > In case of Delimited text files, currently, we always TRIM the input data. > The enhancement request is to make this behaviour configurable, and let user determine, whether the leading or trailing spaces for the column text should be trimmed or not. > Refer thread https://developer.jboss.org/message/905658?et=watches.email.thread#905658 for complete background discussion. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3165) TeiidDataSource ignores jassName

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3165?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3165: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1151034|https://bugzilla.redhat.com/show_bug.cgi?id=1151034] from NEW to MODIFIED > TeiidDataSource ignores jassName > -------------------------------- > > Key: TEIID-3165 > URL: https://issues.jboss.org/browse/TEIID-3165 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: fedora 20 > arch: x86_64 > java: sun 1.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > > I am trying to connect to VDB through Kerberos authentication using TeiidDataSource: > TeiidDataSource tds = new TeiidDataSource(); > tds.setServerName("localhost"); > tds.setPortNumber(31000); > tds.setDatabaseName(<vdb>); > tds.setJaasName(<jassName>); > tds.setKerberosServicePrincipleName(<principalName>); > but tds.getConnection(); ends with: > TEIID20005 Client URL connection property missing "jaasName". Please add the property to connection URL > Connection through TeiidDriver works fine: > url: jdbc:teiid:<vdb>@mm://<host>:31000;jaasName=<jassName>;kerberosServicePrincipleName=<principalName> -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3167) Enhance TEXTTABLE to support TRIM as a configurable option for Delimited Text Files

by Shiveeta Mattoo (JIRA)

Shiveeta Mattoo created TEIID-3167: -------------------------------------- Summary: Enhance TEXTTABLE to support TRIM as a configurable option for Delimited Text Files Key: TEIID-3167 URL: https://issues.jboss.org/browse/TEIID-3167 Project: Teiid Issue Type: Enhancement Environment: Teiid 8.8.0 Final Reporter: Shiveeta Mattoo Assignee: Steven Hawkins In case of Delimited text files, currently, we always TRIM the input data. The enhancement request is to make this behaviour configurable, and let user determine, whether the leading or trailing spaces for the column text should be trimmed or not. Refer thread https://developer.jboss.org/message/905658?et=watches.email.thread#905658 for complete background discussion. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3165) TeiidDataSource ignores jassName

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3165?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3165. ----------------------------------- Fix Version/s: 8.7.1 8.9 Resolution: Done Moved the property logic into the common build properties method. > TeiidDataSource ignores jassName > -------------------------------- > > Key: TEIID-3165 > URL: https://issues.jboss.org/browse/TEIID-3165 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: fedora 20 > arch: x86_64 > java: sun 1.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > > I am trying to connect to VDB through Kerberos authentication using TeiidDataSource: > TeiidDataSource tds = new TeiidDataSource(); > tds.setServerName("localhost"); > tds.setPortNumber(31000); > tds.setDatabaseName(<vdb>); > tds.setJaasName(<jassName>); > tds.setKerberosServicePrincipleName(<principalName>); > but tds.getConnection(); ends with: > TEIID20005 Client URL connection property missing "jaasName". Please add the property to connection URL > Connection through TeiidDriver works fine: > url: jdbc:teiid:<vdb>@mm://<host>:31000;jaasName=<jassName>;kerberosServicePrincipleName=<principalName> -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2014