[JBoss JIRA] (TEIID-3112) Incorrect plural name with parent to child join
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3112?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3112.
-----------------------------------
Resolution: Done
Added the extension metadata property label_plural to set an alternate plural name besides [Name]s. For dynamic vdbs the label will be retrieved from the metadata. If the label is not set we'll assume that we just add s.
> Incorrect plural name with parent to child join
> -----------------------------------------------
>
> Key: TEIID-3112
> URL: https://issues.jboss.org/browse/TEIID-3112
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Salesforce Connector
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> The salesforce logic assumes the plural name can be created with just an 's' at the end, however objects such as Opportunity do not follow that pattern.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIID-3073) Tableau Connection Issues
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3073?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3073:
---------------------------------------
There doesn't seem to be anything directly correlated with the the function support. We'll have to look more to see if some of the metadata queries are attempting to get function information. Beyond that it's using unsupported syntax for teiid such as the on commit clause for creating a temporary table and select top. Is there any way to adjust the dialect that tableau is using against teiid?
> Tableau Connection Issues
> -------------------------
>
> Key: TEIID-3073
> URL: https://issues.jboss.org/browse/TEIID-3073
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ODBC, Server
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Attachments: server.log
>
>
> It has been reported that using Tableu with Teiid ODBC port show the following errors. These need to be investigated and fixed
> {code}
> This ODBC driver does not support important capabilities used by Tableau.
> This unsupported function is required for relative date filters: The date part named 'week' for the date function: DATETRUNC(date_part, date, [start_of_week])
> -----
> Tableau identified the following warnings for the ODBC data source named 'streamyx_sales (streamyx_sales.streamyx_sales) (TMJDV)':
> This aggregation is unsupported: Attribute
> This aggregation is unsupported: Std. Dev
> This aggregation is unsupported: Std. Dev (Pop.)
> This aggregation is unsupported: Trunc Week Number
> This aggregation is unsupported: Variance
> This aggregation is unsupported: Variance (Pop.)
> This function is unsupported: % with parameter types 'integer, integer'
> This function is unsupported: ABS(number) with parameter types 'float'
> This function is unsupported: ABS(number) with parameter types 'integer'
> This function is unsupported: ACOS(number) with parameter types 'float'
> This function is unsupported: ASCII(string) with parameter types 'string'
> This function is unsupported: ASIN(number) with parameter types 'float'
> This function is unsupported: ATAN(number) with parameter types 'float'
> This function is unsupported: ATAN2(y number, x number) with parameter types 'float, float'
> This function is unsupported: CHAR(integer) with parameter types 'float'
> This function is unsupported: CHAR(integer) with parameter types 'integer'
> This function is unsupported: COS(angle) with parameter types 'float'
> This function is unsupported: COT(angle) with parameter types 'float'
> This function is unsupported: DATEPART_DAYOFWEEK_INTERNAL with parameter types 'date'
> This function is unsupported: DATEPART_WEEK_INTERNAL with parameter types 'date'
> This function is unsupported: DATETIME with parameter types 'integer'
> This function is unsupported: DEGREES(number) with parameter types 'float'
> This function is unsupported: EXP(number) with parameter types 'float'
> This function is unsupported: LN with parameter types 'float'
> This function is unsupported: LN(number) with parameter types 'float'
> This function is unsupported: LOG with parameter types 'float'
> This function is unsupported: LOG(number, [base]) with parameter types 'float'
> This function is unsupported: PI()
> This function is unsupported: POWER with parameter types 'float, integer'
> This function is unsupported: POWER with parameter types 'integer, integer'
> This function is unsupported: POWER(number,power) with parameter types 'float, integer'
> This function is unsupported: POWER(number,power) with parameter types 'integer, integer'
> This function is unsupported: RADIANS(number) with parameter types 'float'
> This function is unsupported: ROUND(number, [decimals]) with parameter types 'float'
> This function is unsupported: ROUND(number, [decimals]) with parameter types 'float, integer'
> This function is unsupported: SIGN(number) with parameter types 'float'
> This function is unsupported: SIN(angle) with parameter types 'float'
> This function is unsupported: SPACE with parameter types 'float'
> This function is unsupported: SPACE(number) with parameter types 'integer'
> This function is unsupported: SQRT(number) with parameter types 'float'
> This function is unsupported: SQUARE with parameter types 'float'
> This function is unsupported: TAN(angle) with parameter types 'float'
> This function is unsupported: The date part named 'week' for the date function: DATEDIFF(date_part, start_date, end_date, [start_of_week])
> This function is unsupported: The date part named 'week' for the date function: DATEDIFF(date_part, start_date, end_date, [start_of_week])
> This function is unsupported: The date part named 'week' for the date function: DATENAME(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'week' for the date function: DATENAME(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'week' for the date function: DATEPART(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'week' for the date function: DATEPART(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'weekday' for the date function: DATENAME(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'weekday' for the date function: DATENAME(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'weekday' for the date function: DATEPART(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'weekday' for the date function: DATEPART(date_part, date, [start_of_week])
> This is unsupported: SELECT ... INTO
> This is unsupported: Temporary tables
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIID-3073) Tableau Connection Issues
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3073?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-3073:
--------------------------------
Attachment: server.log
I ran tableau the following is the log with org.teiid.ODBC set to DEBUG
> Tableau Connection Issues
> -------------------------
>
> Key: TEIID-3073
> URL: https://issues.jboss.org/browse/TEIID-3073
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ODBC, Server
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Attachments: server.log
>
>
> It has been reported that using Tableu with Teiid ODBC port show the following errors. These need to be investigated and fixed
> {code}
> This ODBC driver does not support important capabilities used by Tableau.
> This unsupported function is required for relative date filters: The date part named 'week' for the date function: DATETRUNC(date_part, date, [start_of_week])
> -----
> Tableau identified the following warnings for the ODBC data source named 'streamyx_sales (streamyx_sales.streamyx_sales) (TMJDV)':
> This aggregation is unsupported: Attribute
> This aggregation is unsupported: Std. Dev
> This aggregation is unsupported: Std. Dev (Pop.)
> This aggregation is unsupported: Trunc Week Number
> This aggregation is unsupported: Variance
> This aggregation is unsupported: Variance (Pop.)
> This function is unsupported: % with parameter types 'integer, integer'
> This function is unsupported: ABS(number) with parameter types 'float'
> This function is unsupported: ABS(number) with parameter types 'integer'
> This function is unsupported: ACOS(number) with parameter types 'float'
> This function is unsupported: ASCII(string) with parameter types 'string'
> This function is unsupported: ASIN(number) with parameter types 'float'
> This function is unsupported: ATAN(number) with parameter types 'float'
> This function is unsupported: ATAN2(y number, x number) with parameter types 'float, float'
> This function is unsupported: CHAR(integer) with parameter types 'float'
> This function is unsupported: CHAR(integer) with parameter types 'integer'
> This function is unsupported: COS(angle) with parameter types 'float'
> This function is unsupported: COT(angle) with parameter types 'float'
> This function is unsupported: DATEPART_DAYOFWEEK_INTERNAL with parameter types 'date'
> This function is unsupported: DATEPART_WEEK_INTERNAL with parameter types 'date'
> This function is unsupported: DATETIME with parameter types 'integer'
> This function is unsupported: DEGREES(number) with parameter types 'float'
> This function is unsupported: EXP(number) with parameter types 'float'
> This function is unsupported: LN with parameter types 'float'
> This function is unsupported: LN(number) with parameter types 'float'
> This function is unsupported: LOG with parameter types 'float'
> This function is unsupported: LOG(number, [base]) with parameter types 'float'
> This function is unsupported: PI()
> This function is unsupported: POWER with parameter types 'float, integer'
> This function is unsupported: POWER with parameter types 'integer, integer'
> This function is unsupported: POWER(number,power) with parameter types 'float, integer'
> This function is unsupported: POWER(number,power) with parameter types 'integer, integer'
> This function is unsupported: RADIANS(number) with parameter types 'float'
> This function is unsupported: ROUND(number, [decimals]) with parameter types 'float'
> This function is unsupported: ROUND(number, [decimals]) with parameter types 'float, integer'
> This function is unsupported: SIGN(number) with parameter types 'float'
> This function is unsupported: SIN(angle) with parameter types 'float'
> This function is unsupported: SPACE with parameter types 'float'
> This function is unsupported: SPACE(number) with parameter types 'integer'
> This function is unsupported: SQRT(number) with parameter types 'float'
> This function is unsupported: SQUARE with parameter types 'float'
> This function is unsupported: TAN(angle) with parameter types 'float'
> This function is unsupported: The date part named 'week' for the date function: DATEDIFF(date_part, start_date, end_date, [start_of_week])
> This function is unsupported: The date part named 'week' for the date function: DATEDIFF(date_part, start_date, end_date, [start_of_week])
> This function is unsupported: The date part named 'week' for the date function: DATENAME(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'week' for the date function: DATENAME(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'week' for the date function: DATEPART(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'week' for the date function: DATEPART(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'weekday' for the date function: DATENAME(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'weekday' for the date function: DATENAME(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'weekday' for the date function: DATEPART(date_part, date, [start_of_week])
> This function is unsupported: The date part named 'weekday' for the date function: DATEPART(date_part, date, [start_of_week])
> This is unsupported: SELECT ... INTO
> This is unsupported: Temporary tables
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIID-3098) Expose the ModeShape JCR functions in the modeshape translator metadata
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3098?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3098:
---------------------------------------
I believe this issue should be changed to either:
"allow pushdown functions to be schema scoped" ostensibly for the purpose of designer metadata import - with the supporting logic that such functions when imported for multiple sources will not be seen as duplicates.
or "allow discovery of pushdown functions in ddl" - which presumably would mean that they would reside in their existing pseudo sys location. However it's not quite clear in this case what designer would do to represent this on their end unless they introduced special handling.
> Expose the ModeShape JCR functions in the modeshape translator metadata
> ------------------------------------------------------------------------
>
> Key: TEIID-3098
> URL: https://issues.jboss.org/browse/TEIID-3098
> Project: Teiid
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> Expose the ModeShape JCR functions in the metadata in the modeshape translator.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIID-3113) Incorrect parent name for child to parent query
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3113:
-------------------------------------
Summary: Incorrect parent name for child to parent query
Key: TEIID-3113
URL: https://issues.jboss.org/browse/TEIID-3113
Project: Teiid
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Salesforce Connector
Affects Versions: 7.7
Reporter: Steven Hawkins
Assignee: Mark Drilling
Fix For: 8.9
The parent relationship is named based upon the foreign key column which typically is [Some Object]Id, but can be ParentId, etc. which need for example Parent rather than the object name in the source query.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIID-3112) Incorrect plural name with parent to child join
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3112:
-------------------------------------
Summary: Incorrect plural name with parent to child join
Key: TEIID-3112
URL: https://issues.jboss.org/browse/TEIID-3112
Project: Teiid
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Salesforce Connector
Affects Versions: 7.7
Reporter: Steven Hawkins
Assignee: Mark Drilling
Fix For: 8.9
The salesforce logic assumes the plural name can be created with just an 's' at the end, however objects such as Opportunity do not follow that pattern.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIID-2927) Guard against external entity resolving in OData Atom Feed
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2927?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2927.
-----------------------------------
Resolution: Done
Marking as resolved.
> Guard against external entity resolving in OData Atom Feed
> ----------------------------------------------------------
>
> Key: TEIID-2927
> URL: https://issues.jboss.org/browse/TEIID-2927
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: OData, Query Engine
> Affects Versions: 7.7, 8.4
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Critical
> Fix For: 8.7.1
>
>
> OData4j is responsible for parsing the Atom feed. StaxXMLFactoryProvider2 simply creates XMLInputFactories without any options, thus they will perform external entity resolving by default. An issue will need to be opened against OData4j.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months