November 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2738) REST procedure not imported correctly from dynamic VDB

by Andrej Šmigala (JIRA)

Andrej Šmigala created TEIIDDES-2738: ---------------------------------------- Summary: REST procedure not imported correctly from dynamic VDB Key: TEIIDDES-2738 URL: https://issues.jboss.org/browse/TEIIDDES-2738 Project: Teiid Designer Issue Type: Bug Components: Import/Export, VDB & Execution Affects Versions: 9.0.4 Reporter: Andrej Šmigala When importing a dynamic VDB with REST procedure, the created procedure does not have the REST options set. {code:xml} <?xml version="1.0" encoding="UTF-8" standalone="no"?> <vdb name="RestProcedureVdbDynamic" version="1"> <description /> <property name="{http://teiid.org/rest}auto-generate" value="true" /> <model name="ProcedureModel" type="VIRTUAL"> <metadata type="DDL"><![CDATA[ SET NAMESPACE 'http://teiid.org/rest' AS REST; CREATE VIRTUAL PROCEDURE testProc (p1 string(4000)) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}') AS BEGIN SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out; END; ]]></metadata> </model> </vdb> {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2737) Generate VDB Archive and Models from Dynamic VDB file changes integer datatype to biginteger

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2737?page=com.atlassian.jira.plu... ] Debbie Steigner updated TEIIDDES-2737: -------------------------------------- Attachment: Testcase-integer-vdb.xml > Generate VDB Archive and Models from Dynamic VDB file changes integer datatype to biginteger > -------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2737 > URL: https://issues.jboss.org/browse/TEIIDDES-2737 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.2 > Reporter: Debbie Steigner > Attachments: Testcase-integer-vdb.xml > > > Import vdb-xml into teiid-vdb: attribute with integer type gets converted into biginteger type, expected integer type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2737) Generate VDB Archive and Models from Dynamic VDB file changes integer datatype to biginteger

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2737?page=com.atlassian.jira.plu... ] Debbie Steigner reassigned TEIIDDES-2737: ----------------------------------------- Assignee: Barry LaFond > Generate VDB Archive and Models from Dynamic VDB file changes integer datatype to biginteger > -------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2737 > URL: https://issues.jboss.org/browse/TEIIDDES-2737 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.2 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Attachments: Testcase-integer-vdb.xml > > > Import vdb-xml into teiid-vdb: attribute with integer type gets converted into biginteger type, expected integer type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2737) Generate VDB Archive and Models from Dynamic VDB file changes integer datatype to biginteger

by Debbie Steigner (JIRA)

Debbie Steigner created TEIIDDES-2737: ----------------------------------------- Summary: Generate VDB Archive and Models from Dynamic VDB file changes integer datatype to biginteger Key: TEIIDDES-2737 URL: https://issues.jboss.org/browse/TEIIDDES-2737 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 9.2 Reporter: Debbie Steigner Import vdb-xml into teiid-vdb: attribute with integer type gets converted into biginteger type, expected integer type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1618) Support partition statistics

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1618?page=com.atlassian.jira.plu... ] Van Halbert updated TEIIDDES-1618: ---------------------------------- Fix Version/s: 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: 9.2.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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2736) Expose all the materialized properties that Teiid supports for configuration

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-2736: ------------------------------------- Summary: Expose all the materialized properties that Teiid supports for configuration Key: TEIIDDES-2736 URL: https://issues.jboss.org/browse/TEIIDDES-2736 Project: Teiid Designer Issue Type: Enhancement Components: Modeling Affects Versions: 9.2 Reporter: Van Halbert When changing a view to be materialized, should expose all the possible properties that can be configured to control the materialized process. Maybe this is a usability issue, for which I'm not seeing what's there, but its not obvious. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2736) Expose all the materialized properties that Teiid supports for configuration

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2736?page=com.atlassian.jira.plu... ] Van Halbert reassigned TEIIDDES-2736: ------------------------------------- Assignee: Barry LaFond > Expose all the materialized properties that Teiid supports for configuration > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2736 > URL: https://issues.jboss.org/browse/TEIIDDES-2736 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Barry LaFond > > When changing a view to be materialized, should expose all the possible properties that can be configured to control the materialized process. Maybe this is a usability issue, for which I'm not seeing what's there, but its not obvious. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2414) Large transformation SQL is not exported to INDEX file.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2414?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-2414: ------------------------------------------ It looks like there is a hard coded limit on any word of 65k bytes in a UTF encoding, which you could hit next. However there is also something called a record continuation, which looks like it could be used to break up a given record into multiple parts. > Large transformation SQL is not exported to INDEX file. > ------------------------------------------------------- > > Key: TEIIDDES-2414 > URL: https://issues.jboss.org/browse/TEIIDDES-2414 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3.4 > Reporter: Hisanobu Okuda > Assignee: Paul Richardson > Fix For: 9.2.1 > > Attachments: reosurce-problem-marker.png, test.csv > > > A large transformation SQL of a view model is not exported to INDEX file. > I have a large transformation SQL > 8192 bytes in my view model. TDesigner fails to convert the xmi to XXXXXXXXXX.INDEX file. There is no transformation SQL in the INDEX file, therefore, deploying my vdb fails and the vdb is inactivated. When you deploy the vdb, you can see the following message in a log file:- > {code} > 17:16:11,632 WARN [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 2) TEIID31079 View ViewModel.new_table is not defined by a query expression. > 17:16:11,636 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID40073 The metadata for the VDB test.1 is loaded, however it is not valid. Check models for errors. Correct the metadata and re-deploy. > 17:16:11,637 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID40003 VDB test.1 is set to FAILED > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2735) Using fully qualified names creates invalid table names

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2735?page=com.atlassian.jira.plu... ] Steven Hawkins moved TEIID-3833 to TEIIDDES-2735: ------------------------------------------------- Project: Teiid Designer (was: Teiid) Key: TEIIDDES-2735 (was: TEIID-3833) Affects Version/s: 9.0.3 (was: 8.7.1) > Using fully qualified names creates invalid table names > ------------------------------------------------------- > > Key: TEIIDDES-2735 > URL: https://issues.jboss.org/browse/TEIIDDES-2735 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.3 > Environment: Red Hat JBoss Data Virtualization 6.2 on EAP6.4.0 patched to version 6.4.3, > JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157 > 64-bit Windows 7 environment > Reporter: Steve Tran > Assignee: Steven Hawkins > Attachments: step1.PNG, step2.PNG > > > When I import a JDBC datasource and am asked if I want to Use Fully Qualified Names, doing so will cause errors later when trying to deploy the VDB. It doesn't like periods in the table names. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2735) Using fully qualified names creates invalid table names

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2735?page=com.atlassian.jira.plu... ] Steven Hawkins reassigned TEIIDDES-2735: ---------------------------------------- Assignee: (was: Steven Hawkins) Designer should allow the use of . in names except for columns. > Using fully qualified names creates invalid table names > ------------------------------------------------------- > > Key: TEIIDDES-2735 > URL: https://issues.jboss.org/browse/TEIIDDES-2735 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.3 > Environment: Red Hat JBoss Data Virtualization 6.2 on EAP6.4.0 patched to version 6.4.3, > JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157 > 64-bit Windows 7 environment > Reporter: Steve Tran > Attachments: step1.PNG, step2.PNG > > > When I import a JDBC datasource and am asked if I want to Use Fully Qualified Names, doing so will cause errors later when trying to deploy the VDB. It doesn't like periods in the table names. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues November 2015