October 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2714) Buffer defrag not working

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2714: ------------------------------------- Summary: Buffer defrag not working Key: TEIID-2714 URL: https://issues.jboss.org/browse/TEIID-2714 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.6 The defrag task is not working as expected because the header values are written by an object output stream - and not as standalone values into the block data. For most data usage patterns this isn't an issue as the storage files are self compacting over time due to low block assignments. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2704) DB2 sql/xml values must be read inline

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2704?page=com.atlassian.jira.plugin... ] Steven Hawkins reopened TEIID-2704: ----------------------------------- Reopening for all lob values > DB2 sql/xml values must be read inline > -------------------------------------- > > Key: TEIID-2704 > URL: https://issues.jboss.org/browse/TEIID-2704 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.6 > > > With the DB2 9 driver and selecting an xml column. The resulting DB2Xml instance becomes invalid after the next row of the result is transitioned to. > We can compensate for this by retrieving the value as a string. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1675) Add capability to insert/update/delete multi-value attributes in LDAP connector

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-1675?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-1675: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 780736|https://bugzilla.redhat.com/show_bug.cgi?id=780736] from NEW to CLOSED > Add capability to insert/update/delete multi-value attributes in LDAP connector > ------------------------------------------------------------------------------- > > Key: TEIID-1675 > URL: https://issues.jboss.org/browse/TEIID-1675 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 7.4 > Reporter: Marc Shirley > Fix For: Open To Community > > > Add ability to insert/update/delete multi-value attributes through the LDAP connector. For example, this would present the opportunity for maintaining group membership through modifying the list of member attribute values in an LDAP groupOfNames object. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2712) AdminAPI getDataSourceNames is returning the pool name instead of jndi name

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2712?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2712: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1023216 > AdminAPI getDataSourceNames is returning the pool name instead of jndi name > --------------------------------------------------------------------------- > > Key: TEIID-2712 > URL: https://issues.jboss.org/browse/TEIID-2712 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Fix For: 8.4.1, 8.6 > > > See related designer jira. The api call is returning the pool names. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2696) Update Teiid datasource examples to be fully parameterized

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2696?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2696: ------------------------------------ I committed another set of changes for a majority of the jdbc sources. There are a few others that still need to be adapted. > Update Teiid datasource examples to be fully parameterized > ---------------------------------------------------------- > > Key: TEIID-2696 > URL: https://issues.jboss.org/browse/TEIID-2696 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > Fix For: 8.4.1, 8.6 > > > Change the example datasources to be parameterized, and add an associated properties file so that to install, run: > jboss-cli.sh -c --file={datasource}-ds.cli --properties=/{datasource}-ds.properties -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2696) Update Teiid datasource examples to be fully parameterized

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2696?page=com.atlassian.jira.plugin... ] Work on TEIID-2696 stopped by Van Halbert. > Update Teiid datasource examples to be fully parameterized > ---------------------------------------------------------- > > Key: TEIID-2696 > URL: https://issues.jboss.org/browse/TEIID-2696 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > Fix For: 8.4.1, 8.6 > > > Change the example datasources to be parameterized, and add an associated properties file so that to install, run: > jboss-cli.sh -c --file={datasource}-ds.cli --properties=/{datasource}-ds.properties -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2678) Query against OData source throwing java.lang.NullPointerException

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2678?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2678: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1012634|https://bugzilla.redhat.com/show_bug.cgi?id=1012634] from ASSIGNED to MODIFIED > Query against OData source throwing java.lang.NullPointerException > ------------------------------------------------------------------ > > Key: TEIID-2678 > URL: https://issues.jboss.org/browse/TEIID-2678 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Labels: alpha1 > Fix For: 8.4.1, 8.6 > > > Queries against a deployed vdb (using odata translator) are throwing java.lang.NullPointerException. The vdb is connecting to NetWeaver Flight test site . Full log is attached along with vdb. Resource-adapter can be provided if needed. This failure has been verified by two different users. > 12:47:16,401 ERROR [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue13) Connector worker process failed for atomic-request=t53q6HQwO5Rs.6.0.0: java.lang.NullPointerException > at org.odata4j.format.xml.AtomFeedFormatParser.getEntitySet(AtomFeedFormatParser.java:304) > at org.odata4j.format.xml.AtomFeedFormatParser.parse(AtomFeedFormatParser.java:156) > at org.odata4j.format.xml.AtomFeedFormatParser.parse(AtomFeedFormatParser.java:44) > at org.teiid.translator.odata.BaseQueryExecution.parse(BaseQueryExecution.java:93) > at org.teiid.translator.odata.BaseQueryExecution.executeWithReturnEntity(BaseQueryExecution.java:124) > at org.teiid.translator.odata.ODataQueryExecution.execute(ODataQueryExecution.java:108) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:254) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2] > It should also be noted that when previewing FlightCollection in Designer the following error was produced. Not sure if it is related to the server NullPointer situation. > 2:46:00,788 INFO [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue12) TEIID31105 Returing warning to client: TEIID17013 Wrong response from source with status 404 code 005056A509B11EE1B9A8FEC11C21D78E and message Resource not found for the segment 'flightDetails_distanceUnit'. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2712) AdminAPI getDataSourceNames is returning the pool name instead of jndi name

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2712?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2712. --------------------------------- Resolution: Done Removed the filter to allow jndi-name be included with other properties > AdminAPI getDataSourceNames is returning the pool name instead of jndi name > --------------------------------------------------------------------------- > > Key: TEIID-2712 > URL: https://issues.jboss.org/browse/TEIID-2712 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Fix For: 8.4.1, 8.6 > > > See related designer jira. The api call is returning the pool names. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2712) AdminAPI getDataSourceNames is returning the pool name instead of jndi name

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2712?page=com.atlassian.jira.plugin... ] Ramesh Reddy reopened TEIID-2712: --------------------------------- Yes, I see that Teiid was filtering this property out, I will fix it. > AdminAPI getDataSourceNames is returning the pool name instead of jndi name > --------------------------------------------------------------------------- > > Key: TEIID-2712 > URL: https://issues.jboss.org/browse/TEIID-2712 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Fix For: 8.4.1, 8.6 > > > See related designer jira. The api call is returning the pool names. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2712) AdminAPI getDataSourceNames is returning the pool name instead of jndi name

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIID-2712?page=com.atlassian.jira.plugin... ] Mark Drilling commented on TEIID-2712: -------------------------------------- I am attempting to get the "jndi-name" as recommended above, but it is not in the properties. > AdminAPI getDataSourceNames is returning the pool name instead of jndi name > --------------------------------------------------------------------------- > > Key: TEIID-2712 > URL: https://issues.jboss.org/browse/TEIID-2712 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Fix For: 8.4.1, 8.6 > > > See related designer jira. The api call is returning the pool names. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2013