June 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3517) The oracle importer should offer an option to use integral types

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3517?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3517. ----------------------------------- Fix Version/s: 8.11 (was: 8.12) Resolution: Done added a useIntegralTypes option. This will remove some need for erroneous conversions, but we are conservative with the mapping using the precision - so anything over 18 will map to biginteger. > The oracle importer should offer an option to use integral types > ---------------------------------------------------------------- > > Key: TEIID-3517 > URL: https://issues.jboss.org/browse/TEIID-3517 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > The oracle importer should have an option to map number fields with null or 0 decimal digits to an integral type wide enough to represent the precision. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3511) usage of BITAND function in exists statement results in duplicate rows

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3511?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3511: --------------------------------------- As the plans diverge quite a bit, would it be possible possible to provide post execution query plans showing row counts and/or execute with fewer joins to help narrow in on where something is going wrong? > usage of BITAND function in exists statement results in duplicate rows > ---------------------------------------------------------------------- > > Key: TEIID-3511 > URL: https://issues.jboss.org/browse/TEIID-3511 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.9.1 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Attachments: debugplan_bitand.txt, debugplan_bitand_correct.txt, debugplan_nobitand.txt, debugplan_nobitand_correct.txt > > > I've added the debug plan for the query without the BITAND function and with the BITAND function as an attachment. > The version without the BITAND function returns 438 rows and the version with BITAND function returns 833 rows. I can see however that rows are duplicated in this second result. I've checked this by executing the version with BITAND statement with select *. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3410) OData object URI does not resolve to a usable URL.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3410?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3410: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1208515|https://bugzilla.redhat.com/show_bug.cgi?id=1208515] from ON_QA to ASSIGNED > OData object URI does not resolve to a usable URL. > -------------------------------------------------- > > Key: TEIID-3410 > URL: https://issues.jboss.org/browse/TEIID-3410 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > OData object URI does not resolve to a usable URL. When accessing a VDB via odata with a browser either via JSON or XML the uri listed in the metadata is not valid, it doesn't have the FQN of the table, only the type shows FQN: > "__metadata" : { > "uri" : "http://localhost:8080/odata/ODataRHQ/rhq_agent(10001)", > "type" : "RHQ32.rhq_agent" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3358) Issues with entity set names

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3358?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3358: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1208515|https://bugzilla.redhat.com/show_bug.cgi?id=1208515] from ON_QA to ASSIGNED > Issues with entity set names > ---------------------------- > > Key: TEIID-3358 > URL: https://issues.jboss.org/browse/TEIID-3358 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Labels: Alpha1 > Fix For: 8.7.1.6_2, 8.11, 8.7.3 > > > The entity set name used for sql generation should be the fully qualified name. If there is for example two table with the same names in schemas visible to odata, but one of the tables does not have a key, then an ambiguous name exception will be thrown if an odata url is used with only the base table name. > It also appears that the URI link in the results metadata uses the non-qualified table name, which will have issues in the scenario above. > We may also need to document or add an additional check for ambiguity as the OData4j findEdmEntitySet logic will return the first matching entity, which is generally against our approach to resolving. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3410) OData object URI does not resolve to a usable URL.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3410?page=com.atlassian.jira.plugin... ] Steven Hawkins reopened TEIID-3410: ----------------------------------- No fix was applied. The commit related to TEIID-3358 to oreva just appears to be build related. InternalUtils still needs updated. > OData object URI does not resolve to a usable URL. > -------------------------------------------------- > > Key: TEIID-3410 > URL: https://issues.jboss.org/browse/TEIID-3410 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > OData object URI does not resolve to a usable URL. When accessing a VDB via odata with a browser either via JSON or XML the uri listed in the metadata is not valid, it doesn't have the FQN of the table, only the type shows FQN: > "__metadata" : { > "uri" : "http://localhost:8080/odata/ODataRHQ/rhq_agent(10001)", > "type" : "RHQ32.rhq_agent" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3510) Move the Embedded examples into separate repository

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3510?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3510: ------------------------------------- 1) rename to "teiid-embedded-examples" 2) IMO, we do not need to have a build/kit for this. We are not going to bundle examples with embedded kit. Each example needs to be able to build and run, that you already have. 3) service project should need a better name 4) I do not think we need a "common" module, I prefer the examples be defining all the dependencies inline so that they can be build and run independently. This is why we were suggesting a defining a BOM file, so that you can define that in individual project (does same thing as parent pom doing). 5) remove Teiid specific version number from POM files, this can be 1.0.0-SNAPSHOT 6) Where is org.teiid.example.JDBCUtils class? I can help you transfer the ownership to Teiid, find me on IRC we will do that. > Move the Embedded examples into separate repository > ---------------------------------------------------- > > Key: TEIID-3510 > URL: https://issues.jboss.org/browse/TEIID-3510 > Project: Teiid > Issue Type: Feature Request > Components: Embedded > Affects Versions: 8.11 > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 8.11 > > > Create a separate repository for embedded examples, define a maven BOM file for the dependencies management of all examples, and prepare for further refinement like add xa datasources support, add OAuth/REST service, etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3300) Add SPATIAL_REF_SYS table

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3300?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3300: --------------------------------------- With the current logic no you would not be able to issue an update. An alternative although not as straight-forward would be to update the engine module or the embedded classpath to read an updated CSV file, rather than the default under org/teiid/metadata/spatial_ref_sys.csv > Add SPATIAL_REF_SYS table > ------------------------- > > Key: TEIID-3300 > URL: https://issues.jboss.org/browse/TEIID-3300 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Tom Arnold > Assignee: Steven Hawkins > Labels: spatial > Fix For: 8.11 > > > Implement SPATIAL_REF_SYS table (from the OGC Simple Features spec). This table stores metadata about different coordinate systems and how to tranform between them. See [here|http://en.wikipedia.org/wiki/SRID] and [here|http://www.carocoops.org/resources/doc/postgis/x321.html] for details. > {code} > CREATE TABLE SPATIAL_REF_SYS > ( > SRID INTEGER NOT NULL PRIMARY KEY, > AUTH_NAME CHARACTER VARYING(256), > AUTH_SRID INTEGER, > SRTEXT CHARACTER VARYING(2048) > ) > {code} > https://raw.githubusercontent.com/postgis/postgis/svn-trunk/spatial_ref_s... > This would be used in conjunction with the GeoTools referencing module or Proj4J to transform between coordinate systems in Teiid (ST_Transform function). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3516) JDBC metadata importer does not set scale

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3516?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3516. ----------------------------------- Resolution: Done Updated the importer to look at the decimal digits. > JDBC metadata importer does not set scale > ----------------------------------------- > > Key: TEIID-3516 > URL: https://issues.jboss.org/browse/TEIID-3516 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > The JDBC importer should use the decimal_digits column to set the scale. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3327) Translator for OSIsoft PI

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3327?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3327: ---------------------------------- Fix Version/s: 8.12 Priority: Major (was: Optional) > Translator for OSIsoft PI > ------------------------- > > Key: TEIID-3327 > URL: https://issues.jboss.org/browse/TEIID-3327 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Albert Wong > Fix For: 8.12 > > > We have several customers that are using OSIsoft to get time sliced data. We'd like JDV/Teiid to be able to pull data from OSIsoft (OSIsoft is a data source for JDV/Teiid). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3510) Move the Embedded examples into separate repository

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3510?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-3510: ------------------------------------ [1] is the current example repo, any advice, ideas feel free let me know, also how can I transfer it under teiid in future? [1] https://github.com/kylinsoong/teiid-examples > Move the Embedded examples into separate repository > ---------------------------------------------------- > > Key: TEIID-3510 > URL: https://issues.jboss.org/browse/TEIID-3510 > Project: Teiid > Issue Type: Feature Request > Components: Embedded > Affects Versions: 8.11 > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 8.11 > > > Create a separate repository for embedded examples, define a maven BOM file for the dependencies management of all examples, and prepare for further refinement like add xa datasources support, add OAuth/REST service, etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2015