May 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3482) Multi-source joins should still be partitioned even if not fully pushed

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3482?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3482: --------------------------------------- I wanted to log this, but it likely won't get worked as we can't really do this unless we also project the source name column through all parts of the plan For consistency the resolution here will likely be to turn the implicit option off and require the modeling to explicitly specify the partitioning predicates. We can also introduce an explicit multi-tenancy mode such that a given user will only have access to a specific source or sources (this can be accomplished with row based conditions, but may benefit from something simpler in the context of multi-source). > Multi-source joins should still be partitioned even if not fully pushed > ----------------------------------------------------------------------- > > Key: TEIID-3482 > URL: https://issues.jboss.org/browse/TEIID-3482 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > A deficiency in join planning with multi-source is that partitioning only occurs if the join is pushed. If not pushed then we'll union the results and process a join across all of the results. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3396) Redis Connector

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3396?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3396: --------------------------------------- Hi Devin, Any update on this? If you can sign the CLA, then we should at least be able to use what you have as a start. Thanks, Steve > Redis Connector > ---------------- > > Key: TEIID-3396 > URL: https://issues.jboss.org/browse/TEIID-3396 > Project: Teiid > Issue Type: Enhancement > Components: Connector API > Affects Versions: 8.11 > Reporter: Devin Pinkston > Assignee: Steven Hawkins > Priority: Minor > > Resource Adapter and Translator for Redis store (http://redis.io/) > Using Jedis client (https://github.com/xetorthio/jedis) > https://github.com/pinkdevelops/teiid -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3483) Add an option to use DatabaseMetaData for hive/impala import

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3483?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3483. ----------------------------------- Resolution: Done Added an option to use databasemetadata such that ` is used for the quote character and getting index information is defaulted to false. However given the rapidly changing nature of hive JDBC support, this is not yet the default option. If we find that it consistently works for hive client/server .13+ and later impala versions, then we can make it default to true. > Add an option to use DatabaseMetaData for hive/impala import > ------------------------------------------------------------ > > Key: TEIID-3483 > URL: https://issues.jboss.org/browse/TEIID-3483 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > With minor modifications I've confirmed that hive .13 + can do an import using the standard databasemetadata logic. Also hive .12 with a .13 server seems to have an issue with the describe table statement such that the column types are null. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3483) Add an option to use DatabaseMetaData for hive/impala import

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3483: ------------------------------------- Summary: Add an option to use DatabaseMetaData for hive/impala import Key: TEIID-3483 URL: https://issues.jboss.org/browse/TEIID-3483 Project: Teiid Issue Type: Enhancement Components: JDBC Connector Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.11 With minor modifications I've confirmed that hive .13 + can do an import using the standard databasemetadata logic. Also hive .12 with a .13 server seems to have an issue with the describe table statement such that the column types are null. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3419) Add ability to set a default role across all VDBs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3419?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3419. ----------------------------------- Resolution: Done Added an option data-roles-required to the teiid subsystem configuration. If turned on then deployments without data roles will be rejected. > Add ability to set a default role across all VDBs > ------------------------------------------------- > > Key: TEIID-3419 > URL: https://issues.jboss.org/browse/TEIID-3419 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.11 > > > There should be an ability to either set a default role across the server, or to restrict access by default. For example, all VDBs have a default user role that is applied before the VDB specific roles are. Alternatively, there could be a system wide flag that toggles the behavior of VDBs when no roles are defined between accessible to all or denied to all. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3471) unable to consume odata service deployed in teiid

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3471?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3471: -------------------------------- Fix Version/s: 8.7.1.6_2 > unable to consume odata service deployed in teiid > ------------------------------------------------- > > Key: TEIID-3471 > URL: https://issues.jboss.org/browse/TEIID-3471 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.7.1.6_2, 8.11 > > Attachments: deployment-exception.txt, MyVDB-vdb.xml, standalone-snippet.xml > > > I am unable to consume odata service created in teiid. > Steps to reproduce and files are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3482) Multi-source joins should still be partitioned even if not fully pushed

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3482: ------------------------------------- Summary: Multi-source joins should still be partitioned even if not fully pushed Key: TEIID-3482 URL: https://issues.jboss.org/browse/TEIID-3482 Project: Teiid Issue Type: Quality Risk Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.11 A deficiency in join planning with multi-source is that partitioning only occurs if the join is pushed. If not pushed then we'll union the results and process a join across all of the results. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3481) Wrong syntax of cache hints in the documentation

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3481?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3481. ----------------------------------- Resolution: Done Thanks, it looks like it was just an over site when it was first added to the docs. > Wrong syntax of cache hints in the documentation > ------------------------------------------------- > > Key: TEIID-3481 > URL: https://issues.jboss.org/browse/TEIID-3481 > Project: Teiid > Issue Type: Bug > Components: Documentation > Affects Versions: 8.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > The syntax for cache hint is as follows: > (1) cache[([pref_mem] [ttl:n] [updatable])] [scope:(session|user|vdb)] > So if user wants to use cache for specific scope (e.g. session) according to declared syntax it should be: > (2) cache scope:session > But using (2) teiid ignores the scope. What teiid accepts is: > cache(scope:session) > So I suggest to update (1) to: > cache[([pref_mem] [ttl:n] [updatable] [scope:(session|user|vdb)]*)]* -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3481) Wrong syntax of cache hints in the documentation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3481?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3481: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1222520 > Wrong syntax of cache hints in the documentation > ------------------------------------------------- > > Key: TEIID-3481 > URL: https://issues.jboss.org/browse/TEIID-3481 > Project: Teiid > Issue Type: Bug > Components: Documentation > Affects Versions: 8.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > The syntax for cache hint is as follows: > (1) cache[([pref_mem] [ttl:n] [updatable])] [scope:(session|user|vdb)] > So if user wants to use cache for specific scope (e.g. session) according to declared syntax it should be: > (2) cache scope:session > But using (2) teiid ignores the scope. What teiid accepts is: > cache(scope:session) > So I suggest to update (1) to: > cache[([pref_mem] [ttl:n] [updatable] [scope:(session|user|vdb)]*)]* -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3481) Wrong syntax of cache hints in the documentation

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-3481: ----------------------------------- Summary: Wrong syntax of cache hints in the documentation Key: TEIID-3481 URL: https://issues.jboss.org/browse/TEIID-3481 Project: Teiid Issue Type: Bug Components: Documentation Affects Versions: 8.7 Reporter: Juraj Duráni Assignee: Steven Hawkins The syntax for cache hint is as follows: (1) cache[([pref_mem] [ttl:n] [updatable])] [scope:(session|user|vdb)] So if user wants to use cache for specific scope (e.g. session) according to declared syntax it should be: (2) cache scope:session But using (2) teiid ignores the scope. What teiid accepts is: cache(scope:session) So I suggest to update (1) to: cache[([pref_mem] [ttl:n] [updatable] [scope:(session|user|vdb)]*)]* -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 May 2015