April 2016 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2834) Local project name baked into VDB

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2834?page=com.atlassian.jira.plu... ] Steven Hawkins reassigned TEIIDDES-2834: ---------------------------------------- Assignee: (was: Steven Hawkins) > Local project name baked into VDB > --------------------------------- > > Key: TEIIDDES-2834 > URL: https://issues.jboss.org/browse/TEIIDDES-2834 > Project: Teiid Designer > Issue Type: Bug > Environment: Red Hat JBoss Data Virtualization 6.2.4 on EAP patched to version 6.4.6, on Oracle Linux 6 > JBoss Developer Studio 8.1.0GA with Teiid Designer 9.0.6.Final-v20160316-1409-B1242 org.teiid.designer.feature.feature.group JBoss by Red Hat, Inc. > 64-bit Windows 7 environment > Reporter: Steve Tran > > With any source control tool, if I clone/checkout a VDB project, the name of the project must match the name it was created with. All the internal references are using an absolute path with the original project name as the root. This makes VDB projects less portable because someone who comes in and does a git clone <git url> <their_name> will have an unstable project unless they change <their_name> to what the VDB is hard-coded to. > I'm seeing if there's a workaround, such as renaming the internal references, but it looks like a lot of work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2792) Starting JDV/EAP within JBDS throws initialization error

by Steve Tran (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2792?page=com.atlassian.jira.plu... ] Steve Tran commented on TEIIDDES-2792: -------------------------------------- We can close this out. This is no longer an issue as tested with 9.0.6. > Starting JDV/EAP within JBDS throws initialization error > -------------------------------------------------------- > > Key: TEIIDDES-2792 > URL: https://issues.jboss.org/browse/TEIIDDES-2792 > 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: Barry LaFond > Priority: Minor > Attachments: Capture.PNG > > > When starting jDV/EAP within JBDS, a non-fatal error is thrown every time. It can be ignored, but it's an annoyance that customers have reported. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2663) Document Optimal JDBC Parameters for SAP HANA Import

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2663?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2663: -------------------------------------- Assignee: Ted Jones (was: David Le Sage) > Document Optimal JDBC Parameters for SAP HANA Import > ---------------------------------------------------- > > Key: TEIIDDES-2663 > URL: https://issues.jboss.org/browse/TEIIDDES-2663 > Project: Teiid Designer > Issue Type: Task > Components: Documentation, Patch Release > Affects Versions: 9.0.4 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 10.0.2 > > > In order to import SAP HANA metadata, there are a couple of parameter values that help decrease the import time. > For example: > schemaPattern={targetSchema} > tableTypes=TABLE -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2663) Document Optimal JDBC Parameters for SAP HANA Import

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2663?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2663: ----------------------------------- Fix Version/s: (was: 9.2.1) > Document Optimal JDBC Parameters for SAP HANA Import > ---------------------------------------------------- > > Key: TEIIDDES-2663 > URL: https://issues.jboss.org/browse/TEIIDDES-2663 > Project: Teiid Designer > Issue Type: Task > Components: Documentation, Patch Release > Affects Versions: 9.0.4 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 10.0.2 > > > In order to import SAP HANA metadata, there are a couple of parameter values that help decrease the import time. > For example: > schemaPattern={targetSchema} > tableTypes=TABLE -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2663) Document Optimal JDBC Parameters for SAP HANA Import

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2663?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2663: ----------------------------------- Fix Version/s: 10.0.2 (was: 10.0.1) > Document Optimal JDBC Parameters for SAP HANA Import > ---------------------------------------------------- > > Key: TEIIDDES-2663 > URL: https://issues.jboss.org/browse/TEIIDDES-2663 > Project: Teiid Designer > Issue Type: Task > Components: Documentation, Patch Release > Affects Versions: 9.0.4 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 10.0.2 > > > In order to import SAP HANA metadata, there are a couple of parameter values that help decrease the import time. > For example: > schemaPattern={targetSchema} > tableTypes=TABLE -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2823) "Generate Dynamic VDB" utility should use correct property names

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2823?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2823: ----------------------------------- Release Notes Text: (was: 10.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/1875a6fb45d803be1...) > "Generate Dynamic VDB" utility should use correct property names > ---------------------------------------------------------------- > > Key: TEIIDDES-2823 > URL: https://issues.jboss.org/browse/TEIIDDES-2823 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs > Affects Versions: 9.2 > Reporter: Colin Mondesir > Assignee: Barry LaFond > Fix For: 10.0.1 > > > When we generate a Dynamic VDB from a Multisource VDB the output contains: > <property name="supports-multi-source-bindings" value="true"/> > As far as I can see this is the old property name, I believe the designer to use the new "multisource" property name instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2823) "Generate Dynamic VDB" utility should use correct property names

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2823?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2823: ---------------------------------------- 10.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/1875a6fb45d803be1... > "Generate Dynamic VDB" utility should use correct property names > ---------------------------------------------------------------- > > Key: TEIIDDES-2823 > URL: https://issues.jboss.org/browse/TEIIDDES-2823 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs > Affects Versions: 9.2 > Reporter: Colin Mondesir > Assignee: Barry LaFond > Fix For: 10.0.1 > > > When we generate a Dynamic VDB from a Multisource VDB the output contains: > <property name="supports-multi-source-bindings" value="true"/> > As far as I can see this is the old property name, I believe the designer to use the new "multisource" property name instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2823) "Generate Dynamic VDB" utility should use correct property names

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2823?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2823. ------------------------------------ Release Notes Text: 10.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/1875a6fb45d803be1... Resolution: Done > "Generate Dynamic VDB" utility should use correct property names > ---------------------------------------------------------------- > > Key: TEIIDDES-2823 > URL: https://issues.jboss.org/browse/TEIIDDES-2823 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs > Affects Versions: 9.2 > Reporter: Colin Mondesir > Assignee: Barry LaFond > Fix For: 10.0.1 > > > When we generate a Dynamic VDB from a Multisource VDB the output contains: > <property name="supports-multi-source-bindings" value="true"/> > As far as I can see this is the old property name, I believe the designer to use the new "multisource" property name instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2831) Vdb conversion should exclude model 'checksum' and 'index' properties

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2831?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2831. ------------------------------------ Resolution: Done Done > Vdb conversion should exclude model 'checksum' and 'index' properties > --------------------------------------------------------------------- > > Key: TEIIDDES-2831 > URL: https://issues.jboss.org/browse/TEIIDDES-2831 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 10.0 > Reporter: Paul Richardson > Assignee: Paul Richardson > Fix For: 10.0 > > > Conversion of an xmi vdb to a dynamic vdb simply copies all properties contained in models. However, this includes both the 'checksum' and 'indexName' properties which are not applicable to dynamic vdbs. Worse still this is counter-productive since the Dynamic Vdb Sequencers in Komodo actually use the 'indexName' property to determine if the model is Declarative or not, excluding those models with the property present. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2831) Vdb conversion should exclude model 'checksum' and 'index' properties

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2831?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2831: ----------------------------------- Fix Version/s: 10.0.1 (was: 10.0) > Vdb conversion should exclude model 'checksum' and 'index' properties > --------------------------------------------------------------------- > > Key: TEIIDDES-2831 > URL: https://issues.jboss.org/browse/TEIIDDES-2831 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 10.0 > Reporter: Paul Richardson > Assignee: Paul Richardson > Fix For: 10.0.1 > > > Conversion of an xmi vdb to a dynamic vdb simply copies all properties contained in models. However, this includes both the 'checksum' and 'indexName' properties which are not applicable to dynamic vdbs. Worse still this is counter-productive since the Dynamic Vdb Sequencers in Komodo actually use the 'indexName' property to determine if the model is Declarative or not, excluding those models with the property present. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues April 2016