April 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2017) CLONE - wrong type on model in VDB definition

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2017?page=com.atlassian.jira.plugin... ] Steven Hawkins moved TEIIDDES-1329 to TEIID-2017: ------------------------------------------------- Project: Teiid (was: Teiid Designer) Key: TEIID-2017 (was: TEIIDDES-1329) Affects Version/s: 7.6 (was: 7.6) Component/s: Query Engine (was: VDB & Execution) > CLONE - wrong type on model in VDB definition > --------------------------------------------- > > Key: TEIID-2017 > URL: https://issues.jboss.org/browse/TEIID-2017 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.6 > Environment: Windows > Reporter: luca gioppo > > In a VDB created for transforming relational data to XML from exixting XSD the VDB insert "TYPE" in the model description in the manifest file as shown below: > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <vdb version="1" name="libri"> > <property value="false" name="preview"/> > <model visible="true" type="PHYSICAL" name="local_book" path="/books/local_book.xmi"> > <property value="1841187605" name="checksum"/> > <property value="false" name="builtIn"/> > <property value="440299790.INDEX" name="indexName"/> > <source translator-name="mysql5" connection-jndi-name="java:/local_book" name="local_book"/> > </model> > <model visible="true" type="TYPE" name="Books" path="/books/Books.xsd"> > <property value="2392354248" name="checksum"/> > <property value="false" name="builtIn"/> > <property value="4008441630.INDEX" name="indexName"/> > <property value="/books/BookDatatypes.xsd" name="imports"/> > </model> > <model visible="true" type="TYPE" name="BookDatatypes" path="/books/BookDatatypes.xsd"> > <property value="3412846293" name="checksum"/> > <property value="false" name="builtIn"/> > <property value="3680615365.INDEX" name="indexName"/> > </model> > <model visible="true" type="VIRTUAL" name="libro" path="/books/libro.xmi"> > <property value="1493944231" name="checksum"/> > <property value="false" name="builtIn"/> > <property value="2863148665.INDEX" name="indexName"/> > <property value="/books/Books.xsd" name="imports"/> > <property value="/books/BookDatatypes.xsd" name="imports"/> > <property value="/books/local_book.xmi" name="imports"/> > <validation-error path="bookListingDocument/bookListing/sequence/book/type" severity="WARNING">The XML Schema component type for "type" must be marked as an enterprise datatype to be used in this model.</validation-error> > <validation-error path="bookListingDocument/bookListing/sequence/book/isbn" severity="WARNING">The XML Schema component type for "isbn" must be marked as an enterprise datatype to be used in this model.</validation-error> > <validation-error path="bookListingDocument/Mapping Class Set Container/Mapping Classes/book" severity="WARNING">Possible cross-join: Group/s '[local_book.aria.books, local_book.aria.publishers]' are not joined either directly or transitively to other groups through a join criteria. Check all queries in the transformation.</validation-error> > <validation-error path="bookListingDocument/bookListing/sequence/book/sequence/edition" severity="WARNING">"edition" has a fixed or default value and should not be mapped. (See validation Preferences)</validation-error> > <validation-error path="bookListingDocument/bookListing/sequence/book/sequence/title" severity="WARNING">The XML Schema component type for "title" must be marked as an enterprise datatype to be used in this model.</validation-error> > <validation-error path="bookListingDocument/bookListing/sequence/book/sequence/edition" severity="WARNING">The XML Schema component type for "edition" must be marked as an enterprise datatype to be used in this model.</validation-error> > <validation-error path="bookListingDocument/bookListing/sequence/book/sequence/publishDate" severity="WARNING">The XML Schema component type for "publishDate" must be marked as an enterprise datatype to be used in this model.</validation-error> > </model> > </vdb> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (TEIID-1897) Fix the Teiid Build so that the java docs can be built on the first pass

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-1897?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-1897: ------------------------------------------------ Len DiMaggio <ldimaggi(a)redhat.com> changed the Status of [bug 781194|https://bugzilla.redhat.com/show_bug.cgi?id=781194] from ASSIGNED to ON_QA > Fix the Teiid Build so that the java docs can be built on the first pass > ------------------------------------------------------------------------ > > Key: TEIID-1897 > URL: https://issues.jboss.org/browse/TEIID-1897 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 7.7.1 > > Attachments: teiid-javadoc-aggregator.patch > > > In order to build the javadocs in the Teiid project, 2 maven build passes are required to be run. This is because of the order of maven dependencies, causing the javadoc's to fail because the jar's have not been built. A suggested fix is to move the javadocs build into its own project, similarly to how modeshape resolved this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (TEIID-1897) Fix the Teiid Build so that the java docs can be built on the first pass

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1897?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1897: --------------------------------------- As many of the dependencies were incorrect, I have pulled this out for 8.x. They can either be redone or a different workaround will be needed later. > Fix the Teiid Build so that the java docs can be built on the first pass > ------------------------------------------------------------------------ > > Key: TEIID-1897 > URL: https://issues.jboss.org/browse/TEIID-1897 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 7.7.1 > > Attachments: teiid-javadoc-aggregator.patch > > > In order to build the javadocs in the Teiid project, 2 maven build passes are required to be run. This is because of the order of maven dependencies, causing the javadoc's to fail because the jar's have not been built. A suggested fix is to move the javadocs build into its own project, similarly to how modeshape resolved this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (TEIID-1897) Fix the Teiid Build so that the java docs can be built on the first pass

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-1897?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-1897: ------------------------------------------------ Douglas Palmer <dpalmer(a)redhat.com> made a comment on [bug 781194|https://bugzilla.redhat.com/show_bug.cgi?id=781194] Yes, I can confirm that this is fixed > Fix the Teiid Build so that the java docs can be built on the first pass > ------------------------------------------------------------------------ > > Key: TEIID-1897 > URL: https://issues.jboss.org/browse/TEIID-1897 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 7.7.1 > > Attachments: teiid-javadoc-aggregator.patch > > > In order to build the javadocs in the Teiid project, 2 maven build passes are required to be run. This is because of the order of maven dependencies, causing the javadoc's to fail because the jar's have not been built. A suggested fix is to move the javadocs build into its own project, similarly to how modeshape resolved this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (TEIID-1999) Feature Request - auto generate primary key for model results

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIID-1999?page=com.atlassian.jira.plugin... ] Barry LaFond moved TEIIDDES-361 to TEIID-1999: ---------------------------------------------- Project: Teiid (was: Teiid Designer) Key: TEIID-1999 (was: TEIIDDES-361) Component/s: (was: Modeling) Fix Version/s: (was: Future) > Feature Request - auto generate primary key for model results > ------------------------------------------------------------- > > Key: TEIID-1999 > URL: https://issues.jboss.org/browse/TEIID-1999 > Project: Teiid > Issue Type: Feature Request > Reporter: Debbie Steigner > > When the results from a Metadata model search, return data that doesn't have a natural row identifier > (e.g. results from a web search, where only text is returned) is there a way to auto generate a simple primary key identifier value, e.g. rowid in oracle -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (TEIID-1997) Add the ability to support Oracle synonyms

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIID-1997?page=com.atlassian.jira.plugin... ] Barry LaFond resolved TEIID-1997. --------------------------------- Resolution: Duplicate Issue Same as TEIIDDES-226 > Add the ability to support Oracle synonyms > ------------------------------------------- > > Key: TEIID-1997 > URL: https://issues.jboss.org/browse/TEIID-1997 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 6.0.0 > Reporter: Erica Langhi > Priority: Minor > > Currently Teiid Designer doesn't provide the ability > to recognize synonyms. > It would be very beneficial to add this feature as synonyms > are commonly used -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (TEIID-1997) Add the ability to support Oracle synonyms

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIID-1997?page=com.atlassian.jira.plugin... ] Barry LaFond moved TEIIDDES-130 to TEIID-1997: ---------------------------------------------- Project: Teiid (was: Teiid Designer) Key: TEIID-1997 (was: TEIIDDES-130) Affects Version/s: 6.0.0 (was: 6.0.0) Component/s: (was: Modeling) Fix Version/s: (was: Future) > Add the ability to support Oracle synonyms > ------------------------------------------- > > Key: TEIID-1997 > URL: https://issues.jboss.org/browse/TEIID-1997 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 6.0.0 > Reporter: Erica Langhi > Priority: Minor > > Currently Teiid Designer doesn't provide the ability > to recognize synonyms. > It would be very beneficial to add this feature as synonyms > are commonly used -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (TEIID-1994) Regression in latest 7.7.1 code

by Andriy Rokhmanov (JIRA)

Andriy Rokhmanov created TEIID-1994: --------------------------------------- Summary: Regression in latest 7.7.1 code Key: TEIID-1994 URL: https://issues.jboss.org/browse/TEIID-1994 Project: Teiid Issue Type: Bug Affects Versions: 7.7 Environment: Windows 7, java version "1.7.0_02" Java(TM) SE Runtime Environment (build 1.7.0_02-b13) Java HotSpot(TM) 64-Bit Server VM (build 22.0-b10, mixed mode) Reporter: Andriy Rokhmanov Assignee: Steven Hawkins Priority: Critical We build locally a fresh Teiid every Sunday from http://anonsvn.jboss.org/repos/teiid/branches/7.7.x Latest version (built Apr 8, 2012 3:16:17 AM Central) has a regression - some of our integration tests fails with the exception like the one below: 08 Apr 2012 23:38:33,663 CDT ERROR [org.teiid.PROCESSOR] (Worker10_QueryProcessorQueue2542) Unexpected exception for request JQGDo45Wdt99.0 java.lang.NullPointerException at org.teiid.dqp.internal.process.RequestWorkItem.setAnalysisRecords(RequestWorkItem.java:713) at org.teiid.dqp.internal.process.RequestWorkItem.createResultsMessage(RequestWorkItem.java:701) at org.teiid.dqp.internal.process.RequestWorkItem.sendResultsIfNeeded(RequestWorkItem.java:650) at org.teiid.dqp.internal.process.RequestWorkItem$1.flushBatchDirect(RequestWorkItem.java:539) at org.teiid.query.processor.BatchCollector.flushBatch(BatchCollector.java:174) at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:149) at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:374) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:287) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:215) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:232) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:118) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:288) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) As workaround we use the last week version (Teiid built on Apr 1, 2012 3:16:17 AM Central) - our build and all tests completes successfully. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2012