March 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4110) Odata - date functions does't accept date string as a parameter

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4110?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4110: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1322536 Bugzilla Update: Perform > Odata - date functions does't accept date string as a parameter > --------------------------------------------------------------- > > Key: TEIID-4110 > URL: https://issues.jboss.org/browse/TEIID-4110 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Michal Sanitrak > Assignee: Ramesh Reddy > > Date functions year, month, day, hour, minute and second doesn't accept date string(DateTimeOffset) as a parameter. > Reference service which supports OData V4: > *ULR:* http://services.odata.org/V4/Northwind/Northwind.svc/Employees/?$filter=m... eq EmployeeID > *Result:* Employee with ID 1 > *URL:* http://localhost:8080/odata4/olingo_basic/Source/SimpleDataTable/?$filter... eq intkey > *Result:* {"error": {"code": null, "message": "TEIID30069 The function 'MONTH(?)' has more than one possible signature." }} > *Expected result:* Entity with intkey 1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4110) Odata - date functions does't accept date string as a parameter

by Michal Sanitrak (JIRA)

[ https://issues.jboss.org/browse/TEIID-4110?page=com.atlassian.jira.plugin... ] Michal Sanitrak updated TEIID-4110: ----------------------------------- Description: Date functions year, month, day, hour, minute and second doesn't accept date string(DateTimeOffset) as a parameter. Reference service which supports OData V4: *ULR:* http://services.odata.org/V4/Northwind/Northwind.svc/Employees/?$filter=m... eq EmployeeID *Result:* Employee with ID 1 *URL:* http://localhost:8080/odata4/olingo_basic/Source/SimpleDataTable/?$filter... eq intkey *Result:* {"error": {"code": null, "message": "TEIID30069 The function 'MONTH(?)' has more than one possible signature." }} *Expected result:* Entity with intkey 1 was: Date functions year, month, day, hour, minute and second doesn't accept date string(DateTimeOffset) as a parameter. Reference service which supports OData V4: *ULR:* http://services.odata.org/V4/Northwind/Northwind.svc/Employees/?$filter=m... eq EmployeeID *Result:* Employee with ID 1 *URL:* http://localhost:8080/odata4/olingo_basic/Source/SimpleDataTable/?$filter... eq intkey Result:* {"error": {"code": null, "message": "TEIID30069 The function 'MONTH(?)' has more than one possible signature." }} *Expected result:* Entity with intkey 1 > Odata - date functions does't accept date string as a parameter > --------------------------------------------------------------- > > Key: TEIID-4110 > URL: https://issues.jboss.org/browse/TEIID-4110 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Michal Sanitrak > Assignee: Ramesh Reddy > > Date functions year, month, day, hour, minute and second doesn't accept date string(DateTimeOffset) as a parameter. > Reference service which supports OData V4: > *ULR:* http://services.odata.org/V4/Northwind/Northwind.svc/Employees/?$filter=m... eq EmployeeID > *Result:* Employee with ID 1 > *URL:* http://localhost:8080/odata4/olingo_basic/Source/SimpleDataTable/?$filter... eq intkey > *Result:* {"error": {"code": null, "message": "TEIID30069 The function 'MONTH(?)' has more than one possible signature." }} > *Expected result:* Entity with intkey 1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4110) Odata - date functions does't accept date string as a parameter

by Michal Sanitrak (JIRA)

Michal Sanitrak created TEIID-4110: -------------------------------------- Summary: Odata - date functions does't accept date string as a parameter Key: TEIID-4110 URL: https://issues.jboss.org/browse/TEIID-4110 Project: Teiid Issue Type: Sub-task Components: OData Reporter: Michal Sanitrak Assignee: Ramesh Reddy Date functions year, month, day, hour, minute and second doesn't accept date string(DateTimeOffset) as a parameter. Reference service which supports OData V4: *ULR:* http://services.odata.org/V4/Northwind/Northwind.svc/Employees/?$filter=m... eq EmployeeID *Result:* Employee with ID 1 *URL:* http://localhost:8080/odata4/olingo_basic/Source/SimpleDataTable/?$filter... eq intkey Result:* {"error": {"code": null, "message": "TEIID30069 The function 'MONTH(?)' has more than one possible signature." }} *Expected result:* Entity with intkey 1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4106) Rename and align infinispan translators/resource-adapters for their purpose

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4106?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4106: ---------------------------------- Fix Version/s: 9.0 Not necessarily. We just want to minimize breaking changes in minor releases, so if this goes in 9.1 we'll want to be more careful potentially - of course there's still compatibility to consider with 8.12.x. > Rename and align infinispan translators/resource-adapters for their purpose > ---------------------------------------------------------------------------- > > Key: TEIID-4106 > URL: https://issues.jboss.org/browse/TEIID-4106 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.0 > > > The infinispan-cache and infinispan-cache-dsl translators/resource-adapters need to be renamed and aligned for what their purpose is. Because using "dsl" as part of the name is confusing, because both translators now support querying using JDG DSL language. > infinispan-cache: > - rename to infinispan-cache-library-mode (or leave as infinispan-cache and it be assume library mode) > - deprecate the access to remote-cache because the other infinispan-cache-dsl translator provides this feature. > - this will enable the cleaning of the documentation to be specific to library mode > infinispan-cache-dsl: > - rename to infinispan-cache-hot-rod (or something other than "dsl") because this all about remote cache access using hot rod client -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4106) Rename and align infinispan translators/resource-adapters for their purpose

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4106?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4106: ------------------------------------ I would like to. > Rename and align infinispan translators/resource-adapters for their purpose > ---------------------------------------------------------------------------- > > Key: TEIID-4106 > URL: https://issues.jboss.org/browse/TEIID-4106 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Van Halbert > > The infinispan-cache and infinispan-cache-dsl translators/resource-adapters need to be renamed and aligned for what their purpose is. Because using "dsl" as part of the name is confusing, because both translators now support querying using JDG DSL language. > infinispan-cache: > - rename to infinispan-cache-library-mode (or leave as infinispan-cache and it be assume library mode) > - deprecate the access to remote-cache because the other infinispan-cache-dsl translator provides this feature. > - this will enable the cleaning of the documentation to be specific to library mode > infinispan-cache-dsl: > - rename to infinispan-cache-hot-rod (or something other than "dsl") because this all about remote cache access using hot rod client -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4105) ODATA: Duplicate NavigationProperty name

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4105?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4105: ------------------------------------- If that is case I think v4 needs to be revised too, but there whole navigation got simplified so there may not be an issue. > ODATA: Duplicate NavigationProperty name > ---------------------------------------- > > Key: TEIID-4105 > URL: https://issues.jboss.org/browse/TEIID-4105 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.3 > Reporter: Ivan Lucas Vargas > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 9.0, 8.12.5 > > > Entity 1: TransferRule > Entity 2: FinancialAccount > TransferRule > - sourceAccount : FinancialAccount > - destination : FinancialAccount > - other attributes > the mapping to this for odata resolves to > <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_destinationfinancial_account_id_fk" FromRole="transferrule" ToRole="financialaccount" /> > <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_sourcefinancial_account_id_fk" FromRole="transferrule" > ToRole="financialaccount" /> > The navigation property name is duplicated with in transfer rule entity. > Hence some of the Odata client see it as ambiguous element > Is there a way to customise the Name to > Name="src_financialaccount" and > Name="dest_financialaccount" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4106) Rename and align infinispan translators/resource-adapters for their purpose

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4106?page=com.atlassian.jira.plugin... ] Van Halbert edited comment on TEIID-4106 at 3/30/16 12:04 PM: -------------------------------------------------------------- I would like to. Is there any timeline that I need to consider? was (Author: van.halbert): I would like to. > Rename and align infinispan translators/resource-adapters for their purpose > ---------------------------------------------------------------------------- > > Key: TEIID-4106 > URL: https://issues.jboss.org/browse/TEIID-4106 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Van Halbert > > The infinispan-cache and infinispan-cache-dsl translators/resource-adapters need to be renamed and aligned for what their purpose is. Because using "dsl" as part of the name is confusing, because both translators now support querying using JDG DSL language. > infinispan-cache: > - rename to infinispan-cache-library-mode (or leave as infinispan-cache and it be assume library mode) > - deprecate the access to remote-cache because the other infinispan-cache-dsl translator provides this feature. > - this will enable the cleaning of the documentation to be specific to library mode > infinispan-cache-dsl: > - rename to infinispan-cache-hot-rod (or something other than "dsl") because this all about remote cache access using hot rod client -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4106) Rename and align infinispan translators/resource-adapters for their purpose

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4106?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4106: --------------------------------------- Do you think this will be possible in 9.0? > Rename and align infinispan translators/resource-adapters for their purpose > ---------------------------------------------------------------------------- > > Key: TEIID-4106 > URL: https://issues.jboss.org/browse/TEIID-4106 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Van Halbert > > The infinispan-cache and infinispan-cache-dsl translators/resource-adapters need to be renamed and aligned for what their purpose is. Because using "dsl" as part of the name is confusing, because both translators now support querying using JDG DSL language. > infinispan-cache: > - rename to infinispan-cache-library-mode (or leave as infinispan-cache and it be assume library mode) > - deprecate the access to remote-cache because the other infinispan-cache-dsl translator provides this feature. > - this will enable the cleaning of the documentation to be specific to library mode > infinispan-cache-dsl: > - rename to infinispan-cache-hot-rod (or something other than "dsl") because this all about remote cache access using hot rod client -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4105) ODATA: Duplicate NavigationProperty name

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4105?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4105: ------------------------------------- I thought relationship always between PK in one table and key in another key database, I guess that could be multiple keys. > ODATA: Duplicate NavigationProperty name > ---------------------------------------- > > Key: TEIID-4105 > URL: https://issues.jboss.org/browse/TEIID-4105 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.3 > Reporter: Ivan Lucas Vargas > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 9.0, 8.12.5 > > > Entity 1: TransferRule > Entity 2: FinancialAccount > TransferRule > - sourceAccount : FinancialAccount > - destination : FinancialAccount > - other attributes > the mapping to this for odata resolves to > <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_destinationfinancial_account_id_fk" FromRole="transferrule" ToRole="financialaccount" /> > <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_sourcefinancial_account_id_fk" FromRole="transferrule" > ToRole="financialaccount" /> > The navigation property name is duplicated with in transfer rule entity. > Hence some of the Odata client see it as ambiguous element > Is there a way to customise the Name to > Name="src_financialaccount" and > Name="dest_financialaccount" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4008) Sending teiid varbinary value (x'') to Microsoft SQL Server errors

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4008?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4008. ----------------------------------- Resolution: Done Updated to address the pg select with a cast. > Sending teiid varbinary value (x'') to Microsoft SQL Server errors > ------------------------------------------------------------------ > > Key: TEIID-4008 > URL: https://issues.jboss.org/browse/TEIID-4008 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.7.2.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.7.5.6_2, 8.13.2 > > > When sending a query to Microsoft SQL Server with a varbinary in criteria: > select * from debBinary where ipv6= x'FFFF6BBE85D8' > It pushes the criteria to Microsoft SQL Server, but as X'FFFF6BBE85D8'[1] so Microsoft gives the syntax error[2] and needs to just be select * from debBinary where ipv6= 'FFFF6BBE85D8': > [1]14:26:08,951 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue8) Source-specific command: SELECT g_0."id", g_0."ipv6" FROM "bqt2"."dbo"."debbinary" g_0 WHERE g_0."ipv6" = X'FFFF6BBE85D8' > [2] com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near 'FFFF6BBE85D8'. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2016