October 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5078) Expand docs on CXF logging

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5078?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5078. ----------------------------------- Resolution: Done Updated the ws and salseforce resource adapter pages. > Expand docs on CXF logging > -------------------------- > > Key: TEIID-5078 > URL: https://issues.jboss.org/browse/TEIID-5078 > Project: Teiid > Issue Type: Quality Risk > Components: Documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0 > > > The logging section shown in our docs is only valid for jaxws soap services. All other usage of CXF, rest or salesforce (which now just directly uses the webclient), needs to have different logging instructions. > See https://docs.jboss.org/author/display/JBWS/Advanced+User+Guide or the config shown on TEIID-4495 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5078) Expand docs on CXF logging

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5078?page=com.atlassian.jira.plugin... ] Work on TEIID-5078 started by Steven Hawkins. --------------------------------------------- > Expand docs on CXF logging > -------------------------- > > Key: TEIID-5078 > URL: https://issues.jboss.org/browse/TEIID-5078 > Project: Teiid > Issue Type: Quality Risk > Components: Documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0 > > > The logging section shown in our docs is only valid for jaxws soap services. All other usage of CXF, rest or salesforce (which now just directly uses the webclient), needs to have different logging instructions. > See https://docs.jboss.org/author/display/JBWS/Advanced+User+Guide or the config shown on TEIID-4495 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5048) Docs updatable views

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5048?page=com.atlassian.jira.plugin... ] Work on TEIID-5048 started by Steven Hawkins. --------------------------------------------- > Docs updatable views > -------------------- > > Key: TEIID-5048 > URL: https://issues.jboss.org/browse/TEIID-5048 > Project: Teiid > Issue Type: Bug > Components: Documentation > Reporter: Lukáš Svačina > Assignee: Steven Hawkins > Priority: Minor > Fix For: 10.0 > > > Elaborate on updatable/insertable views with joins according to [forum|https://developer.jboss.org/message/975675?et=watches.email.thread#...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5072) Generated keys should be passed from triggers

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5072?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5072. ----------------------------------- Resolution: Done Updated the docs wrt the new system function and the key variable group. > Generated keys should be passed from triggers > --------------------------------------------- > > Key: TEIID-5072 > URL: https://issues.jboss.org/browse/TEIID-5072 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0 > > > In the context of an update trigger we should be able to convey the generated keys to the caller. In the case where only a single insert occurs, this should be automatic. Otherwise we'll need functions/variables to get/set the generated keys in the procedure. For example see the LAST_INSERT_ID function on mysql. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4943) Minimize creating redundant copied predicates

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4943?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4943: ---------------------------------- Description: When an inner join with a predicate that can be copied is pushed, we will still create the copied criteria. In some situations, this over-constraining is not desirable. We should minimize when this occurs. For example: select col1 from t1, t2 where t1.col = t2.col and t1.col = 1 should pushdown as: select col1 from t1, t2 where t1.col = t2.col and t1.col = 1 not: select col1 from t1, t2 where t1.col = t2.col and t1.col = 1 and t2.col = 1 was:When an inner join with a predicate that can be copied is pushed, we will still create the copied criteria. In some situations, this over-constraining is not desirable. There should be a capability to determine if this copying should take place. Summary: Minimize creating redundant copied predicates (was: Allow translators to declare if copied criteria should be included) > Minimize creating redundant copied predicates > --------------------------------------------- > > Key: TEIID-4943 > URL: https://issues.jboss.org/browse/TEIID-4943 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0 > > > When an inner join with a predicate that can be copied is pushed, we will still create the copied criteria. In some situations, this over-constraining is not desirable. We should minimize when this occurs. For example: > select col1 from t1, t2 where t1.col = t2.col and t1.col = 1 > should pushdown as: > select col1 from t1, t2 where t1.col = t2.col and t1.col = 1 > not: > select col1 from t1, t2 where t1.col = t2.col and t1.col = 1 and t2.col = 1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4943) Allow translators to declare if copied criteria should be included

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4943?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4943. ----------------------------------- Resolution: Done Changed the planning behavior to only push the copied criteria in specific circumstances, rather than generally even when we are already under an access node. This mostly, but not completely, addresses the referenced forum post. There are still circumstances involving delayed pushdown, or greater transitivity (such as three tables all joined by the same columns), that would still result in the copied predicate being pushed. > Allow translators to declare if copied criteria should be included > ------------------------------------------------------------------ > > Key: TEIID-4943 > URL: https://issues.jboss.org/browse/TEIID-4943 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0 > > > When an inner join with a predicate that can be copied is pushed, we will still create the copied criteria. In some situations, this over-constraining is not desirable. There should be a capability to determine if this copying should take place. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4854) Google translator fails to update timestamp value reformatted after update

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4854?page=com.atlassian.jira.plugin... ] Work on TEIID-4854 started by Steven Hawkins. --------------------------------------------- > Google translator fails to update timestamp value reformatted after update > -------------------------------------------------------------------------- > > Key: TEIID-4854 > URL: https://issues.jboss.org/browse/TEIID-4854 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.3, 8.12.10.6_3 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > Fix For: 10.0 > > Attachments: gs-reformatted-timestamp.log > > > Cell of type timestamp is reformatted after an update. Data inserted from teiid are in format "yyyy-mm-dd hh:mm:ss[.fffffffff]", which is reformatted to "dd/mm/yyyy hh:mm:ss[.fffffffff]". Subsequent update of such row throws exception "Could not convert source column Source.smalla.timestampvalue to the expected runtime type timestamp". > Google spreadsheet locale was UK, timezone was set to Berlin. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5095) ElementName is always null when calling sysadmin.usage

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5095?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5095. ----------------------------------- Resolution: Duplicate Issue Duplicate of TEIID-4835 > ElementName is always null when calling sysadmin.usage > ------------------------------------------------------ > > Key: TEIID-5095 > URL: https://issues.jboss.org/browse/TEIID-5095 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.x-6.4 > Reporter: Van Halbert > Assignee: Steven Hawkins > > When perform the following sql in a VDB that has views: > select ElementName from sysadmin.usage > the element name is always -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5095) ElementName is always null when calling sysadmin.usage

by Van Halbert (JIRA)

Van Halbert created TEIID-5095: ---------------------------------- Summary: ElementName is always null when calling sysadmin.usage Key: TEIID-5095 URL: https://issues.jboss.org/browse/TEIID-5095 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.12.x-6.4 Reporter: Van Halbert Assignee: Steven Hawkins When perform the following sql in a VDB that has views: select ElementName from sysadmin.usage the element name is always -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5094) Is DISTINCT FROM evaluation with two null values

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-5094?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-5094: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1500079|https://bugzilla.redhat.com/show_bug.cgi?id=1500079] from NEW to ASSIGNED > Is DISTINCT FROM evaluation with two null values > ------------------------------------------------ > > Key: TEIID-5094 > URL: https://issues.jboss.org/browse/TEIID-5094 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 10.0, 8.12.x-6.4, 9.3.4, 9.2.7 > > > 'row(null) is distinct from row(null)" evaluates to true when false is expected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2017