July 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4977) Support materialization as the 8.12.x version did

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4977?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4977: -------------------------------- Attachment: ispn-vdb.xml > Support materialization as the 8.12.x version did > ------------------------------------------------- > > Key: TEIID-4977 > URL: https://issues.jboss.org/browse/TEIID-4977 > Project: Teiid > Issue Type: Feature Request > Components: Infinispan > Affects Versions: 8.12.x-6.4 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Attachments: ispn-vdb.xml > > > Need to enable the materialization process to load the cache "offline" and not impact access to current cache and data. This would be similar to how the 8.12.x version was implemented and similar to how RDBMS materialization is done. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3722) Add an option to not widen comparisons to string

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3722?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3722: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1460324|https://bugzilla.redhat.com/show_bug.cgi?id=1460324] from ASSIGNED to ON_QA > Add an option to not widen comparisons to string > ------------------------------------------------ > > Key: TEIID-3722 > URL: https://issues.jboss.org/browse/TEIID-3722 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > Our resolving logic considers anything with an implicit conversion to string to be a valid widening conversion in a comparison. For example: > int_col = '1a' > will effectively become cast(int_col as string) = '1a' > Or with timestamps: > timestamp_col = '1970-01-01' > becomes cast(timestamp_col as string) = '1970-01-01' > In equality cases the optimizer will infer that the predicate is simply false, but when used with greater/less than comparison we'll still attempt the query with the widening conversion. > This is most likely not the intent of the user. It would be best to provide an option that would allow an exception to be thrown rather than assuming a query that may not match the user's expectations. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4976) criteria duplicated when criteria includes the same columns as dependent join criteria

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4976?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4976: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1468368, https://bugzilla.redhat.com/show_bug.cgi?id=1466507 Bugzilla Update: Perform > criteria duplicated when criteria includes the same columns as dependent join criteria > -------------------------------------------------------------------------------------- > > Key: TEIID-4976 > URL: https://issues.jboss.org/browse/TEIID-4976 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.11.6_2 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 10.0, 8.12.x-6.4, 8.12.12.6_3, 8.7.13.6_2 > > > Submitting a query that uses the same column for the join condition and criteria results in the criteria being duplicated on the dependent side of the join. > For example: > SELECT * FROM A, B > WHERE B.id = A.id AND A.id IN ('1','2','3') OPTION MAKEDEP B; > Results in the dependent side query looking like: > SELECT ... FROM B WHERE B.id IN ('1','2','3') AND B.id IN ('1','2','3'); > This looks to have already been resolved in later versions, but I was not able to find the original JIRA that would have addressed this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4983) Couchbase tests rely on unpredictable order

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4983: ------------------------------------- Summary: Couchbase tests rely on unpredictable order Key: TEIID-4983 URL: https://issues.jboss.org/browse/TEIID-4983 Project: Teiid Issue Type: Bug Components: Misc. Connectors Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 10.0, 8.12.x-6.4 The insert tests and others have metadata built off of json which depending upon the jre may return elements in a different order. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4971) Infinispan Hotrod can't access remote instance

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4971?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4971: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1466180|https://bugzilla.redhat.com/show_bug.cgi?id=1466180] from NEW to MODIFIED > Infinispan Hotrod can't access remote instance > ---------------------------------------------- > > Key: TEIID-4971 > URL: https://issues.jboss.org/browse/TEIID-4971 > Project: Teiid > Issue Type: Bug > Components: Infinispan, JDG Connector > Affects Versions: 8.12.x-6.4 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Priority: Blocker > > The Infinispan Hotrod connector writes to jdg's internal cache, which can't be accessed from remote hosts if the cache container is not secured and the user accessing the internal cache doesn't have specific privileges. > User can't authenticate via resource-adapter currently, enhancement TEIID-4904 is needed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4957) Setting Connection Type on VDB of a Domain Managed server gets set back to default after server restart

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIID-4957?page=com.atlassian.jira.plugin... ] Debbie Steigner commented on TEIID-4957: ---------------------------------------- [~van.halbert] You cannot use the User Properties because it writes to the vdb.xml as <property name="connection-type" value="NONE"/> and it needs to be <connection-type>NONE</connection-type> I already logged that bug as https://issues.jboss.org/browse/TEIIDDES-3087 > Setting Connection Type on VDB of a Domain Managed server gets set back to default after server restart > ------------------------------------------------------------------------------------------------------- > > Key: TEIID-4957 > URL: https://issues.jboss.org/browse/TEIID-4957 > Project: Teiid > Issue Type: Bug > Components: VDB > Affects Versions: 8.12.10.6_3 > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > Fix For: 10.0 > > > After deploying a VDB to a managed server group, set the Connection type to anything but the default of By_Version, so None or Any. Now restart the server and you'll see the Connection type is reset to the default. > What I see is that when the change is made a vdb.xml with that new connection-type is written to the /DVserverhome/domain/servers/server-two/data/teiid-data/SampleVDB_1 folder, this folder is deleted upon a restart though so the change is not kept. > This only happens in Domain mode, running in Standalone mode saves the change because the teiid-data is not deleted on a restart. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4933) Enhance CouchbaseMetadataProcessor to add sampleKeyspaces property and support more typed table name

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4933?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4933: ---------------------------------- Fix Version/s: 9.3 > Enhance CouchbaseMetadataProcessor to add sampleKeyspaces property and support more typed table name > ---------------------------------------------------------------------------------------------------- > > Key: TEIID-4933 > URL: https://issues.jboss.org/browse/TEIID-4933 > Project: Teiid > Issue Type: Enhancement > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 9.3 > > > * add a sampleKeyspaces, default is *, means sample all keyspaces, which same as previous design, if set sampleKeyspaces, then specific Keyspaces be sampled > * add support more typed name in same keyspace, for a sample Keyspace, in some times there may need more typed name to define table name -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4933) Enhance CouchbaseMetadataProcessor to add sampleKeyspaces property and support more typed table name

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4933?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4933: ---------------------------------- Component/s: Misc. Connectors > Enhance CouchbaseMetadataProcessor to add sampleKeyspaces property and support more typed table name > ---------------------------------------------------------------------------------------------------- > > Key: TEIID-4933 > URL: https://issues.jboss.org/browse/TEIID-4933 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 9.3 > > > * add a sampleKeyspaces, default is *, means sample all keyspaces, which same as previous design, if set sampleKeyspaces, then specific Keyspaces be sampled > * add support more typed name in same keyspace, for a sample Keyspace, in some times there may need more typed name to define table name -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4928) Couchbase - NAMEINSOURCE required for all the columns and tables

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4928?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4928: ---------------------------------- Fix Version/s: 9.3 > Couchbase - NAMEINSOURCE required for all the columns and tables > ---------------------------------------------------------------- > > Key: TEIID-4928 > URL: https://issues.jboss.org/browse/TEIID-4928 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.3 > Reporter: Juraj Duráni > Assignee: Kylin Soong > Fix For: 9.3 > > > Option *NAMEINSOURCE* is de facto required for all the columns and tables. If it is not present then: > # column name in source query is not enclosed in back quotes - e.g. *`$cb_t1`.ShortValue* instead of *`$cb_t1`.`ShortValue`* > # name of the table is not added to the source query - e.g. *SELECT ... FROM null `$cb_t1` LET ... WHERE ...* instead of *SELECT ... FROM `smalla` `$cb_t1` LET ... WHERE ...* > This should work OOB without need to add NAMEINSOURCE option. Teiid should automatically translate column name from e.g. *MyColumn* to *`MyColumn`* if option is not set. Same with name of the table. > In case of table I think this is more serious as it does not even try name of the table but supplies *null* to the query -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4972) Couchbase - query with comparison criteria not properly translated

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4972?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4972. ----------------------------------- Resolution: Done > Couchbase - query with comparison criteria not properly translated > ------------------------------------------------------------------ > > Key: TEIID-4972 > URL: https://issues.jboss.org/browse/TEIID-4972 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.x-6.4 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 10.0, 8.12.x-6.4, 9.3.1 > > > Issuing simple query with comparison criteria like \[1\] returns empty result. From what I can see, the query is not properly translated - it is translated to query with syntax error \[2\]. > Another issue here which I can see is that Teiid does not provide any information to the user that query actually failed. Only empty result is returned. This one, I will report it as a separate issue. > {code:sql|title=\[1\] Query} > SELECT BQT1.SmallA.FloatNum FROM BQT1.SmallA WHERE BQT1.SmallA.FloatNum = 7 > {code} > {code:plain|title=\[2\] Source-specific query} > 10:16:09,749 DEBUG [org.teiid.CONNECTOR] (Worker12_QueryProcessorQueue86) TEIID29001 Source-specific Query: SELECT TONUMBER(`$cb_c1_FloatNum`) FROM `dvqe_small` `$cb_t1` LET `$cb_c1_FloatNum` = `$cb_t1`.`FloatNum`TONUMBER() WHERE TONUMBER(`$cb_c1_FloatNum`) = 7.0 AND `$cb_t1`.`type` = 'SmallA' > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 July 2017