[JBoss JIRA] (TEIIDDES-2665) Add an option to not widen comparisons to string
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2665?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2665:
--------------------------------------
Assignee: Paul Richardson
> Add an option to not widen comparisons to string
> ------------------------------------------------
>
> Key: TEIIDDES-2665
> URL: https://issues.jboss.org/browse/TEIIDDES-2665
> Project: Teiid Designer
> Issue Type: Quality Risk
> Components: Teiid Integration
> Reporter: Steven Hawkins
> Assignee: Paul Richardson
> Fix For: 9.2.1
>
>
> 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
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2665) Add an option to not widen comparisons to string
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2665?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2665:
-----------------------------------
Component/s: Patch Release
> Add an option to not widen comparisons to string
> ------------------------------------------------
>
> Key: TEIIDDES-2665
> URL: https://issues.jboss.org/browse/TEIIDDES-2665
> Project: Teiid Designer
> Issue Type: Quality Risk
> Components: Patch Release, Teiid Integration
> Reporter: Steven Hawkins
> Assignee: Paul Richardson
> Fix For: 9.2.1
>
>
> 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
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2684) SalesForce importer issue
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2684?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2684:
-----------------------------------
Component/s: Patch Release
(was: Release Work)
> SalesForce importer issue
> -------------------------
>
> Key: TEIIDDES-2684
> URL: https://issues.jboss.org/browse/TEIIDDES-2684
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release
> Affects Versions: 9.0.4
> Environment: MAC OS
> Reporter: Matus Makovy
> Assignee: Mark Drilling
> Fix For: 9.2.1
>
> Attachments: salesdynamic-vdb.xml
>
>
> According to conversation in TEIID-3112 this is a Designer issue. If I understood correctly, it has been fixed in Teiid and now the changes have to be made in TD SF importer.
> I have a VDB with Source model that is created via SalesForce importer and I am getting this error:
> {quote}
> Didn't understand relationship 'Opportunitys' in FROM part of query call. If you are attempting to use a custom relationship, be sure to append the '__r' after the custom relationship name. Please reference your WSDL or the describe call for the appropriate names
> {quote}
> when trying to submit this query:
> {quote}
> select distinct YEAR("Opportunity"."CloseDate") as "Opportunity_CloseDate1" from "SalesForceSource".Campaign AS "Campaign" LEFT OUTER JOIN "SalesForceSource".Opportunity AS "Opportunity" ON Campaign."Id" = Opportunity."CampaignId" order by YEAR("Opportunity"."CloseDate") ASC LIMIT 0 , 32
> {quote}
> It works without problems with dynamic VDB.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2689) LDAP dialogue too slow - loads a lot of data?
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2689?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2689:
-----------------------------------
Component/s: Import/Export
Patch Release
> LDAP dialogue too slow - loads a lot of data?
> ---------------------------------------------
>
> Key: TEIIDDES-2689
> URL: https://issues.jboss.org/browse/TEIIDDES-2689
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release
> Affects Versions: 9.0.4
> Environment: MAC OS
> Reporter: Matus Makovy
> Assignee: Paul Richardson
> Priority: Critical
> Fix For: 9.2.1
>
> Attachments: Screen Shot 2015-10-14 at 14.17.46.png
>
>
> I came across this when trying to verify TEIIDDES-2478.
> When you have a LDAP instance with big amount of entries (in the screenshot you can see that are 931 entries) in some part, it takes long to load all attributes. After clicking Next> on the page shown in screenshot (see attachment) JBDS freezes and doesn't respond for about 3 minutes. At least we should have some message that says, that TD is loading data from LDAP.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-1386) Cannot multi-select schema contents when building response procedure result set (Web Service as input)
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1386?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1386:
-----------------------------------
Fix Version/s: 10.1
(was: 9.2.1)
> Cannot multi-select schema contents when building response procedure result set (Web Service as input)
> ------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1386
> URL: https://issues.jboss.org/browse/TEIIDDES-1386
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 7.7.1
> Reporter: Paul Nittel
> Assignee: Barry LaFond
> Fix For: 10.1
>
> Attachments: CannotMultiSelect.png
>
>
> When modeling the response result set for an incoming Web Service, the user must select each attribute individually and click the Add button. Intuitively, I tried to multi-select the attributes, but that is not permitted. It should be. :-) Screenshot is attached.
> I used the Oorsprong FullCountryInfo operation which has several output attributes from which to choose.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-1618) Support partition statistics
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1618?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1618:
-----------------------------------
Fix Version/s: 10.1
(was: 9.2.1)
> Support partition statistics
> ----------------------------
>
> Key: TEIIDDES-1618
> URL: https://issues.jboss.org/browse/TEIIDDES-1618
> Project: Teiid Designer
> Issue Type: Feature Request
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 10.1
>
>
> The stats gathering feature does not take into account of partition statistics. Most of our query hit a single partition and using the global stats is not a true indication of the statistics for the single partition. It would be nice if Teiid engine can differentiate the usage of global and partition statistics during the optimisation and planning stages.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-1732) Stream line steps to implement all the steps around materialization
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1732?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1732:
-----------------------------------
Fix Version/s: 10.1
(was: 9.2.1)
> Stream line steps to implement all the steps around materialization
> --------------------------------------------------------------------
>
> Key: TEIIDDES-1732
> URL: https://issues.jboss.org/browse/TEIIDDES-1732
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Affects Versions: 8.2
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 10.1
>
>
> Would like to stream line the steps to putting materialization to work. Example:
> - Right mouse click on view, select materialization
> - present wizard to walk thru the following options:
> - create physical table based on selected view/table (export/import of ddl is supported, but would like the table automatically created)
> - put name of mat table into the selected table/view to be materialized
> - [optional] export DDL (file system or clipboard)
> - [optional] create procedure that has the "select into" for refreshing
> Having the procedure provides the immediate ability to call to refresh, without having to remember what tables. Also, with the feature of native queries, could add the truncate call to clear the table.
> Once thru this wizard, (I think) everything is in place to do materialization for the specified table.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months