October 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2729) Dynamic VDB xml requires sibling elements to be in a certain order

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2729?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2729: ---------------------------------- Fix Version/s: 8.12.1 > Dynamic VDB xml requires sibling elements to be in a certain order > ------------------------------------------------------------------ > > Key: TEIID-2729 > URL: https://issues.jboss.org/browse/TEIID-2729 > Project: Teiid > Issue Type: Enhancement > Components: AdminApi > Affects Versions: 8.5 > Reporter: Mark Drilling > Fix For: 8.12.1 > > > In my *-vdb.xml, I have a model defined per following snippet: > <model name="myModel" type="PHYSICAL" visible="true"> > <source name="myModel" translator-name="hive" connection-jndi-name="Hive12Src" /> > <property name="trimColumnNames" value="true" /> > </model> > The vdb.xml failed to parse, so I moved the <property> element ahead of <source> and then it worked. > I don't think element ordering should matter in this case? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3739) Dynamic VDB that imports another VDB does not get redeployed if the imported VDB is redeployed

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3739?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3739: ------------------------------------- That is by design, imported VDB, could be defined in other VDBs, and materialization caching could have defined, all those needs to be refreshed. what is the usecase behind issue? > Dynamic VDB that imports another VDB does not get redeployed if the imported VDB is redeployed > ---------------------------------------------------------------------------------------------- > > Key: TEIID-3739 > URL: https://issues.jboss.org/browse/TEIID-3739 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Attachments: dynovdb1-vdb.xml, dynovdb2-vdb.xml > > > When using a Dynamic VDB that imports another VDB it isn't redeployed if the imported VDB is redeployed. You can in the log it undeploys the top VDB and the imported VDB but only redeploys the imported one. The top VDB then doesn't exist until it's redeployed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3739) Dynamic VDB that imports another VDB does not get redeployed if the imported VDB is redeployed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3739?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3739: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1268308 Bugzilla Update: Perform > Dynamic VDB that imports another VDB does not get redeployed if the imported VDB is redeployed > ---------------------------------------------------------------------------------------------- > > Key: TEIID-3739 > URL: https://issues.jboss.org/browse/TEIID-3739 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Attachments: dynovdb1-vdb.xml, dynovdb2-vdb.xml > > > When using a Dynamic VDB that imports another VDB it isn't redeployed if the imported VDB is redeployed. You can in the log it undeploys the top VDB and the imported VDB but only redeploys the imported one. The top VDB then doesn't exist until it's redeployed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3739) Dynamic VDB that imports another VDB does not get redeployed if the imported VDB is redeployed

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIID-3739?page=com.atlassian.jira.plugin... ] Debbie Steigner updated TEIID-3739: ----------------------------------- Attachment: dynovdb2-vdb.xml dynovdb1-vdb.xml > Dynamic VDB that imports another VDB does not get redeployed if the imported VDB is redeployed > ---------------------------------------------------------------------------------------------- > > Key: TEIID-3739 > URL: https://issues.jboss.org/browse/TEIID-3739 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Attachments: dynovdb1-vdb.xml, dynovdb2-vdb.xml > > > When using a Dynamic VDB that imports another VDB it isn't redeployed if the imported VDB is redeployed. You can in the log it undeploys the top VDB and the imported VDB but only redeploys the imported one. The top VDB then doesn't exist until it's redeployed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3739) Dynamic VDB that imports another VDB does not get redeployed if the imported VDB is redeployed

by Debbie Steigner (JIRA)

Debbie Steigner created TEIID-3739: -------------------------------------- Summary: Dynamic VDB that imports another VDB does not get redeployed if the imported VDB is redeployed Key: TEIID-3739 URL: https://issues.jboss.org/browse/TEIID-3739 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.7.1.6_2 Reporter: Debbie Steigner Assignee: Steven Hawkins When using a Dynamic VDB that imports another VDB it isn't redeployed if the imported VDB is redeployed. You can in the log it undeploys the top VDB and the imported VDB but only redeploys the imported one. The top VDB then doesn't exist until it's redeployed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3727) Add a latest version of the salesforce connectivity to the server kit

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3727?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3727: --------------------------------------- That makes sense thanks. I'll update the docs. > Add a latest version of the salesforce connectivity to the server kit > --------------------------------------------------------------------- > > Key: TEIID-3727 > URL: https://issues.jboss.org/browse/TEIID-3727 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector, Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > For convenience it would be good to offer a latest salesforce version, rather than requiring users to build a new translator/resource adapter. We can also deprecate the v22 connectivity then. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3727) Add a latest version of the salesforce connectivity to the server kit

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3727?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3727: ------------------------------------- No, it can not. Previous "salesforce" translator is dependent on V22 of partner API, and those are defined in the module.xml. So, in order to avoid that I had to copy the jar and make a new module out of it for V34. > Add a latest version of the salesforce connectivity to the server kit > --------------------------------------------------------------------- > > Key: TEIID-3727 > URL: https://issues.jboss.org/browse/TEIID-3727 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector, Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > For convenience it would be good to offer a latest salesforce version, rather than requiring users to build a new translator/resource adapter. We can also deprecate the v22 connectivity then. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3727) Add a latest version of the salesforce connectivity to the server kit

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3727?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3727: --------------------------------------- Thanks Ramesh. I removed the new jars for the embedded kit as more than likely the approach there is to just replace the salesforce jars - also there was an issue that all of the project dependencies were being pulled in. I saw that the 34 translator is directly including the base translator jar. Should it just depend on the base translator module instead? > Add a latest version of the salesforce connectivity to the server kit > --------------------------------------------------------------------- > > Key: TEIID-3727 > URL: https://issues.jboss.org/browse/TEIID-3727 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector, Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > For convenience it would be good to offer a latest salesforce version, rather than requiring users to build a new translator/resource adapter. We can also deprecate the v22 connectivity then. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3738) Add multi-tenant functionality

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3738: ------------------------------------- Summary: Add multi-tenant functionality Key: TEIID-3738 URL: https://issues.jboss.org/browse/TEIID-3738 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors, Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.0 To supplement multi-source functionality, we should add explicit multi-tenant functionality similar to hibernate - http://docs.jboss.org/hibernate/orm/4.2/devguide/en-US/html/ch16.html This would mostly be carried out at the datasource level, but would also make us cache aware. Otherwise our current story is to implement multi-source and add row level filters to all multi-source tables to prune based upon the user - which we could choose to expand on in Designer or the server such that the necessary roles are created automatically. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3736) Allow date formatted string literals to be parsed as timestamps

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3736?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3736. ----------------------------------- Resolution: Done Added by directly resolving the string literals to constants so that the general string to timestamp conversion would remain the same. This is different than the other resolving logic in that it does alter the string form of the query. > Allow date formatted string literals to be parsed as timestamps > --------------------------------------------------------------- > > Key: TEIID-3736 > URL: https://issues.jboss.org/browse/TEIID-3736 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > For consistency with most major vendors we should support allowing date literals to be parsed as timestamps. For example: > timestamp_col > '2001-01-01' > which would prevent the predicate from being resolved as a string comparison. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2015