April 2016 - teiid-issues - Jboss List Archives

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4008?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4008: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1313407|https://bugzilla.redhat.com/show_bug.cgi?id=1313407] from ON_QA to VERIFIED > 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.13.2, 8.7.5.6_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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4119) ODBC reports tables as views ('relkind' column in pg_catalog.pg_class) when it should report as table type

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4119?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4119: --------------------------------------- Ignore the previous comment. In re-examining what is being asked for here, there are a couple of clarifications to be made. reportAsViews does not affect this case directly - it will have no influence on odbc behavior. However what the customer is effectively looking for is the inverse of reportAsView for odbc - they want a "base table" added to a virtual model to be reported as a table. In reality any table construct added to a virtual model is a view and will have a view definition. It is a quirk of the metadata system (that was attempting to cover both physical and virtual cases in the same metamodel) as to why it's referred to as a base table when adding a child to the model. Starting with Teiid 7 (which was still consistent with mmx logic), we effectively were only looking at the virtual flag to determine if something is a view. Is there a compelling reason why the customer needs a Teiid virtual table / view reported to their client as a table? If they simply need them reported consistently, then the recommendation would be to use reportAsViews=true for their client connections. Otherwise if they are going directly against SYS.Tables, then they'll need to look at both the type and the virtual flag. > ODBC reports tables as views ('relkind' column in pg_catalog.pg_class) when it should report as table type > ----------------------------------------------------------------------------------------------------------- > > Key: TEIID-4119 > URL: https://issues.jboss.org/browse/TEIID-4119 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 7.7 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.12.5, 8.13.4 > > > Virtual tables are reported as a view with value "v" in 'relkind' column in pg_catalog.pg_class. This should be reported as a table in some cases, so we need to be able to toggle the metadata to report as the type the user needs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4124) add literal date format YYYY-MM-DD to the SQL Server translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4124?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4124: --------------------------------------- We'll work this first trying to avoid using undocumented codes. If that proves too messy, the we'll just rely on the 23 code. > add literal date format YYYY-MM-DD to the SQL Server translator > --------------------------------------------------------------- > > Key: TEIID-4124 > URL: https://issues.jboss.org/browse/TEIID-4124 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.7.2.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > We are missing literal data format YYYY-MM-DD, which is 23 in our mapping for the sqlserver translator: > http://stackoverflow.com/questions/15555275/undocumented-convert-styles-d... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4124) add literal date format YYYY-MM-DD to the SQL Server translator

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4124?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4124: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1325003 Bugzilla Update: Perform > add literal date format YYYY-MM-DD to the SQL Server translator > --------------------------------------------------------------- > > Key: TEIID-4124 > URL: https://issues.jboss.org/browse/TEIID-4124 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.7.2.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > We are missing literal data format YYYY-MM-DD, which is 23 in our mapping for the sqlserver translator: > http://stackoverflow.com/questions/15555275/undocumented-convert-styles-d... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4124) add literal date format YYYY-MM-DD to the SQL Server translator

by Debbie Steigner (JIRA)

Debbie Steigner created TEIID-4124: -------------------------------------- Summary: add literal date format YYYY-MM-DD to the SQL Server translator Key: TEIID-4124 URL: https://issues.jboss.org/browse/TEIID-4124 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 8.7.2.6_2 Reporter: Debbie Steigner Assignee: Steven Hawkins We are missing literal data format YYYY-MM-DD, which is 23 in our mapping for the sqlserver translator: http://stackoverflow.com/questions/15555275/undocumented-convert-styles-d... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4094) Move the packaging of teiid-jdbc.jar into is own project

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4094?page=com.atlassian.jira.plugin... ] Steven Hawkins reopened TEIID-4094: ----------------------------------- This change causes nexus to not allow the build to be closed with the complaint: Missing: no sources jar found in folder '/org/jboss/teiid/teiid-jdbc/9.0.0.Beta1' > Move the packaging of teiid-jdbc.jar into is own project > -------------------------------------------------------- > > Key: TEIID-4094 > URL: https://issues.jboss.org/browse/TEIID-4094 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 8.12.x > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.0, 8.12.5 > > > The issue with the way the teiid-jdbc.jar is packaged now, is that the teiid-web-console.zip gets included as a dependency. > {code} > [INFO] +- org.jboss.teiid:teiid:jar:jdbc:8.12.5.redhat-2:compile > [INFO] | \- org.jboss.teiid.web-console:teiid-console-dist:zip:jboss-as7:2.5.6.Final-redhat-63-4:compile > {code} > And that becomes an issue when other external projects to Teiid include the jdbc driver as a dependency, in that they also end up requiring the web-console.zip. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

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: ------------------------------------ Just to make sure, changing the translators to: ispn-hotrod (was infinispan-cache-hotrod) ispn-lib-mode (was infinispan-cache) > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4123) Issues with odbc metadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4123?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4123. ----------------------------------- Resolution: Done Updated the logic to be more selective in setting the typmod and added types for varbinary and its array type. > Issues with odbc metadata > ------------------------- > > Key: TEIID-4123 > URL: https://issues.jboss.org/browse/TEIID-4123 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.4 > > > The values that we are sending the client for atttypmod in the column when using cursoring results in the pg odbc client reissuing the column metadata query for most column types. Since the column metadata query is not that performant - TEIID-4122 - this results in significant overhead for wide selects. > We also don't have a pg_type entry for varbinary and may need to add more array types. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4122) Improve performance of odbc client column metadata query

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4122?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-4122: ------------------------------------- Fix Version/s: 9.1 (was: 9.0) Assignee: (was: Steven Hawkins) > Improve performance of odbc client column metadata query > -------------------------------------------------------- > > Key: TEIID-4122 > URL: https://issues.jboss.org/browse/TEIID-4122 > Project: Teiid > Issue Type: Quality Risk > Components: ODBC > Reporter: Steven Hawkins > Fix For: 9.1 > > > With cursoring, the client issues: > select n.nspname, c.relname, a.attname, a.atttypid, t.typname, a.attnum, a.attlen, a.atttypmod, a.attnotnull, c.relhasrules, c.relkind, c.oid, pg_get_expr(d.adbin, d.adrelid), case t.typtype when 'd' then t.typbasetype else 0 end, t.typtypmod, c.relhasoids from (((pg_catalog.pg_class c inner join pg_catalog.pg_namespace n on n.oid = c.relnamespace and c.oid = <table oid>) inner join pg_catalog.pg_attribute a on (not a.attisdropped) and a.attnum > 0 and a.attrelid = c.oid) inner join pg_catalog.pg_type t on t.oid = a.atttypid) left outer join pg_attrdef d on a.atthasdef and d.adrelid = a.attrelid and d.adnum = a.attnum order by n.nspname, c.relname, attnum > We should ensure that this is being planned optimally. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4114) Expanding logic in the format conversion for parsing and formatting of dates

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4114?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4114: ------------------------------------------------ Alex Szczuczko <aszczucz(a)redhat.com> changed the Status of [bug 1323312|https://bugzilla.redhat.com/show_bug.cgi?id=1323312] from MODIFIED to ON_QA > Expanding logic in the format conversion for parsing and formatting of dates > ---------------------------------------------------------------------------- > > Key: TEIID-4114 > URL: https://issues.jboss.org/browse/TEIID-4114 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.11 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.7.5.6_2 > > > Java documentation isn't explicit https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html regarding date/time formats. > The format string is not enforced on the parsing side, so any hour format will accept any value. However oracle's behavior is different - if you specify HH vs HH24, then 13-23 is disallowed. > Need to address this by expanding the logic in the format conversion to account for the difference between parsing and formatting. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2016