July 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3454) Dependent Join optimizations for Netezza and Hive

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3454?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3454: ---------------------------------- Fix Version/s: 8.12 > Dependent Join optimizations for Netezza and Hive > ------------------------------------------------- > > Key: TEIID-3454 > URL: https://issues.jboss.org/browse/TEIID-3454 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.10 > Reporter: John Muller > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.12 > > > Currently, dependent joins create 1 or more IN clauses. Many MPP / NoSQL systems can have drastically better performance by creating temp tables that match key distributions. Two examples I know of would be Netezza and Hive. > In Netezza, if the incoming dependent join (small dimension; here "Customer" using Northwind data model concepts) has a key that will be joined to to a big fact table that is DISTRIBUTED ON or ORGANIZED BY 'ed then creating a temp table that matches this distribution will result in ~100x query performance. Sometimes, if the dimension is small enough, this doesn't make a big difference as Netezza will perform a broadcast join, but it's never a bad idea to create the temp table. > Similarly, Hive DDL has both partitions and buckets (pre-sorted). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3454) Dependent Join optimizations for Netezza and Hive

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3454?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3454: ---------------------------------- We'll at least get temp table creation working for 8.12. > Dependent Join optimizations for Netezza and Hive > ------------------------------------------------- > > Key: TEIID-3454 > URL: https://issues.jboss.org/browse/TEIID-3454 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.10 > Reporter: John Muller > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.12 > > > Currently, dependent joins create 1 or more IN clauses. Many MPP / NoSQL systems can have drastically better performance by creating temp tables that match key distributions. Two examples I know of would be Netezza and Hive. > In Netezza, if the incoming dependent join (small dimension; here "Customer" using Northwind data model concepts) has a key that will be joined to to a big fact table that is DISTRIBUTED ON or ORGANIZED BY 'ed then creating a temp table that matches this distribution will result in ~100x query performance. Sometimes, if the dimension is small enough, this doesn't make a big difference as Netezza will perform a broadcast join, but it's never a bad idea to create the temp table. > Similarly, Hive DDL has both partitions and buckets (pre-sorted). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3515) make makedep and related hints consistent

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3515?page=com.atlassian.jira.plugin... ] Work on TEIID-3515 started by Steven Hawkins. --------------------------------------------- > make makedep and related hints consistent > ----------------------------------------- > > Key: TEIID-3515 > URL: https://issues.jboss.org/browse/TEIID-3515 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > There are three places where hints can be specified, in the options clause, after an item, and before in a comment block. > We should ensure that the comment block supports all options max/join for makedep, and that makeind should have the same options as makedep. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3545) Improvements in default handling

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3545?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3545. ----------------------------------- Resolution: Done Added the extension property teiid_rel:default_handling, which can be set to expression to have the default interpreted as an expression or omit to have the parameter omitted from source procedure calls. > Improvements in default handling > -------------------------------- > > Key: TEIID-3545 > URL: https://issues.jboss.org/browse/TEIID-3545 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > The current default field is just a string value and captured as a string value at import time - in general it should be allowed to be an expression. Also our insert syntax should support the default/defaults keywords and be able to propagate that to the source, rather than using the default on the model. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3566) insert value pushed inappropriately

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3566?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3566. ----------------------------------- Resolution: Done Changed the logic to pre-evaluate instead > insert value pushed inappropriately > ----------------------------------- > > Key: TEIID-3566 > URL: https://issues.jboss.org/browse/TEIID-3566 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > An insert with a subquery or other non-pushable construct: > Insert into pm1.g1 (e1) values ((select current_database())) > Will have the subquery pushed to the source query - even if the source does not support it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3566) insert value pushed inappropriately

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3566?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3566: ---------------------------------- Summary: insert value pushed inappropriately (was: Subquery insert value pushed inappropriately) Description: An insert with a subquery or other non-pushable construct: Insert into pm1.g1 (e1) values ((select current_database())) Will have the subquery pushed to the source query - even if the source does not support it. was: An insert with a subquery: Insert into pm1.g1 (e1) values ((select current_database())) Will have the subquery pushed to the source query - even if the source does not support it. > insert value pushed inappropriately > ----------------------------------- > > Key: TEIID-3566 > URL: https://issues.jboss.org/browse/TEIID-3566 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > An insert with a subquery or other non-pushable construct: > Insert into pm1.g1 (e1) values ((select current_database())) > Will have the subquery pushed to the source query - even if the source does not support it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3566) Subquery insert value pushed inappropriately

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3566: ------------------------------------- Summary: Subquery insert value pushed inappropriately Key: TEIID-3566 URL: https://issues.jboss.org/browse/TEIID-3566 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.12 An insert with a subquery: Insert into pm1.g1 (e1) values ((select current_database())) Will have the subquery pushed to the source query - even if the source does not support it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3565) SalesForce.com soap api 23

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3565?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3565: --------------------------------------- Are you saying that you updated the URL to the v 23 api and are seeing an error at import? That is essentially expected - see https://issues.jboss.org/browse/TEIID-3492 > SalesForce.com soap api 23 > -------------------------- > > Key: TEIID-3565 > URL: https://issues.jboss.org/browse/TEIID-3565 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 8.7.3 > Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA > JBoss Data Virtualization 6.1.0.ER4 > Reporter: Jorge Herrera > Assignee: Steven Hawkins > > When importing the definition of the Opportunity Object from SalesForce, the CreditCardNumber field always comes without a data type, it only shows error on the model. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3565) SalesForce.com soap api 23

by Jorge Herrera (JIRA)

[ https://issues.jboss.org/browse/TEIID-3565?page=com.atlassian.jira.plugin... ] Jorge Herrera updated TEIID-3565: --------------------------------- Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA JBoss Data Virtualization 6.1.0.ER4 was:RHEL 6, AWS VM > SalesForce.com soap api 23 > -------------------------- > > Key: TEIID-3565 > URL: https://issues.jboss.org/browse/TEIID-3565 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 8.7.3 > Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA > JBoss Data Virtualization 6.1.0.ER4 > Reporter: Jorge Herrera > Assignee: Steven Hawkins > > When importing the definition of the Opportunity Object from SalesForce, the CreditCardNumber field always comes without a data type, it only shows error on the model. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3565) SalesForce.com soap api 23

by Jorge Herrera (JIRA)

Jorge Herrera created TEIID-3565: ------------------------------------ Summary: SalesForce.com soap api 23 Key: TEIID-3565 URL: https://issues.jboss.org/browse/TEIID-3565 Project: Teiid Issue Type: Bug Components: Salesforce Connector Affects Versions: 8.7.3 Environment: RHEL 6, AWS VM Reporter: Jorge Herrera Assignee: Steven Hawkins When importing the definition of the Opportunity Object from SalesForce, the CreditCardNumber field always comes without a data type, it only shows error on the model. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2015