September 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2655) Minimize the reporting of erroneous illegalstateexceptions

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2655: ------------------------------------- Summary: Minimize the reporting of erroneous illegalstateexceptions Key: TEIID-2655 URL: https://issues.jboss.org/browse/TEIID-2655 Project: Teiid Issue Type: Quality Risk Components: Server Affects Versions: 8.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.5 Service injector illegalstateexceptions can be seen as errors in the logs with asynch metadata load when the vdb has already failed for another reason. We should ensure that these are not reported as additional errors. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2584) Add management features to materialization

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2584: ------------------------------------- In the latest commit, I modified VDB deployer such that the "booting" flag is captured at that time of deploy and passed to the metadata loaders such that even though the boot event is passed by the time metadata is loaded, the vdb is still considered a reload. Also, added to two system functions "token_get", "token_count", using these two functions, the loadMatView will parse the scripts passed through MATVIEW_AFTER_LOAD_SCRIPT, MATVIEW_BEFORE_LOAD_SCRIPT, MATVIEW_LOAD_SCRIPT properties using semicolon (;) as delimiters and execute those tokenized commands one at a time to allow proper execution on databases. > Add management features to materialization > ------------------------------------------ > > Key: TEIID-2584 > URL: https://issues.jboss.org/browse/TEIID-2584 > Project: Teiid > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 8.5 > > > Currently Teiid supports internal and external materialization features. The internal is managed completely by the Teiid query engine along with the infinispan cache. > External materialization is completely unmanaged and left out to the user to manage it externally. This goals for this feature are unify the materialization logic for internal and external, such that both are managed similarly irrespective of the type of materialization chosen. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2584) Add management features to materialization

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIID-2584 at 9/9/13 1:29 PM: ------------------------------------------------------------- In the latest commit, I modified VDB deployer such that the "booting" flag is captured at that time of deploy and passed to the metadata loaders such that even though the boot event is passed by the time metadata is loaded, the vdb is still considered a reload. Also, added to two system functions "token_get", "token_count", using these two functions, the loadMatView will parse the scripts passed through MATVIEW_AFTER_LOAD_SCRIPT, MATVIEW_BEFORE_LOAD_SCRIPT, MATVIEW_LOAD_SCRIPT properties using semicolon (\;) as delimiters and execute those tokenized commands one at a time to allow proper execution on databases. was (Author: rareddy): In the latest commit, I modified VDB deployer such that the "booting" flag is captured at that time of deploy and passed to the metadata loaders such that even though the boot event is passed by the time metadata is loaded, the vdb is still considered a reload. Also, added to two system functions "token_get", "token_count", using these two functions, the loadMatView will parse the scripts passed through MATVIEW_AFTER_LOAD_SCRIPT, MATVIEW_BEFORE_LOAD_SCRIPT, MATVIEW_LOAD_SCRIPT properties using semicolon (;) as delimiters and execute those tokenized commands one at a time to allow proper execution on databases. > Add management features to materialization > ------------------------------------------ > > Key: TEIID-2584 > URL: https://issues.jboss.org/browse/TEIID-2584 > Project: Teiid > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 8.5 > > > Currently Teiid supports internal and external materialization features. The internal is managed completely by the Teiid query engine along with the infinispan cache. > External materialization is completely unmanaged and left out to the user to manage it externally. This goals for this feature are unify the materialization logic for internal and external, such that both are managed similarly irrespective of the type of materialization chosen. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2650) A jboss server in domain mode does not advertise its teiid runtime-version

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIID-2650?page=com.atlassian.jira.plugin... ] Paul Richardson commented on TEIID-2650: ---------------------------------------- Spent time creating queries through the domain master's client(?) servers and this works well. Thanks for the info. However, I do not see why the teiid runtime version is only available through these client servers. Since teiid is deployed onto the domain master rather than its client servers, I don't understand why the runtime version is not available in the location '/profile=ha/subsystem=teiid/runtime-version'. I realise its not a static property and has no place in the config files yet it is filled in correctly when the server is in standalone mode. It seems wrong that its 'undefined' for domain mode when we deploy teiid using the domain master. Maybe, I am still misunderstanding domain mode? > A jboss server in domain mode does not advertise its teiid runtime-version > -------------------------------------------------------------------------- > > Key: TEIID-2650 > URL: https://issues.jboss.org/browse/TEIID-2650 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Reporter: Paul Richardson > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 8.4.1, 8.5 > > > A standalone jboss server installed with teiid advertises its teiid runtime version at the path /subsystem=teiid/runtime-version. > Likewise, a domain jboss server installed with teiid in the 'ha' profile should advertise its runtime version at the path /profile=ha/subsystem=teiid/runtime-version. > However, whereas the standalone returns the correct value for this attribute, the domain mode server fails, only returning 'undefined'. > This attribute is essential to designer in determining what version is the teiid instance. This in turns determines the functionality of the modelling that is available and which teiid client should be used for connection. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2561) Allow nested MERGE of entities in MongoDB translators

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2561?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2561: -------------------------------- Fix Version/s: 8.6 (was: 8.5) > Allow nested MERGE of entities in MongoDB translators > ----------------------------------------------------- > > Key: TEIID-2561 > URL: https://issues.jboss.org/browse/TEIID-2561 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.6 > > > Currently the MERGE (EMBEDIN) functionality can not be nested with other embeddable properties. I.e. if table defined "EMBEDIN", then it's parent can not define any embeddable properties. > 1) Rename EMBEDIN --> MERGE extension property > 2) When MERGE is on child table, Allow parent table to be participate in another "MERGE" or "EMBEDDEBLE" scenario. > This will allow greater number of tables to be collapsed into single document. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2606) Duplicate resource during restart of server with dynamically generated REST WAR file

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2606?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2606. --------------------------------- Resolution: Done finished as part TEIID-2584 > Duplicate resource during restart of server with dynamically generated REST WAR file > ------------------------------------------------------------------------------------ > > Key: TEIID-2606 > URL: https://issues.jboss.org/browse/TEIID-2606 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.1 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.5 > > > I have VDB that is designed to generate the REST WAR file, after the deployment of the VDB, if server is restarted the below error is thrown > {code} > 15:07:26,514 ERROR [org.jboss.as.controller.management-operation] (teiid-async-threads - 4) JBAS014613: Operation ("add") failed - address: ([("deployment" => "sakila_1.war")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"sakila_1.war\")]" > 15:07:26,519 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) Failed to deploy sakila_1.war: org.teiid.adminapi.AdminProcessingException: TEIID70006 {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014803: Duplicate resource [(\"deployment\" => \"sakila_1.war\")]"}} > at org.teiid.adminapi.AdminFactory$AdminImpl.execute(AdminFactory.java:484) [teiid-admin-8.4.1.jar:8.4.1] > at org.teiid.adminapi.AdminFactory$AdminImpl.deploy(AdminFactory.java:749) [teiid-admin-8.4.1.jar:8.4.1] > at org.teiid.jboss.rest.ResteasyEnabler$1.run(ResteasyEnabler.java:94) [teiid-jboss-integration-8.4.1.jar:8.4.1] > at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) > at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:806) > at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45) > at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:847) > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_35] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > {code} -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2654) CXF Logging Configuration Example - Missing Entry?

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2654?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2654. ----------------------------------- Fix Version/s: 8.5 Resolution: Done Added the logging feature class to the bean shown in the example and added another external link. > CXF Logging Configuration Example - Missing Entry? > -------------------------------------------------- > > Key: TEIID-2654 > URL: https://issues.jboss.org/browse/TEIID-2654 > Project: Teiid > Issue Type: Bug > Components: Documentation > Reporter: B Long > Assignee: Steven Hawkins > Fix For: 8.5 > > > Should the example CXF config file given for Logging configuration with Web Services contain the following line: > <bean class="org.apache.cxf.feature.LoggingFeature"/> > Refer to documentation at https://docs.jboss.org/author/display/TEIID/Web+Service+Data+Sources -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2654) CXF Logging Configuration Example - Missing Entry?

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2654?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2654: --------------------------------------- I think that snippet must have originally shown what a typical spring file would look like, and was not specific to logging. It seems like we should reference http://cxf.apache.org/docs/configuration.html and show something similar to one of those snippets. > CXF Logging Configuration Example - Missing Entry? > -------------------------------------------------- > > Key: TEIID-2654 > URL: https://issues.jboss.org/browse/TEIID-2654 > Project: Teiid > Issue Type: Bug > Components: Documentation > Reporter: B Long > Assignee: Steven Hawkins > > Should the example CXF config file given for Logging configuration with Web Services contain the following line: > <bean class="org.apache.cxf.feature.LoggingFeature"/> > Refer to documentation at https://docs.jboss.org/author/display/TEIID/Web+Service+Data+Sources -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2654) CXF Logging Configuration Example - Missing Entry?

by B Long (JIRA)

B Long created TEIID-2654: ----------------------------- Summary: CXF Logging Configuration Example - Missing Entry? Key: TEIID-2654 URL: https://issues.jboss.org/browse/TEIID-2654 Project: Teiid Issue Type: Bug Components: Documentation Reporter: B Long Assignee: Steven Hawkins Should the example CXF config file given for Logging configuration with Web Services contain the following line: <bean class="org.apache.cxf.feature.LoggingFeature"/> Refer to documentation at https://docs.jboss.org/author/display/TEIID/Web+Service+Data+Sources -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2606) Duplicate resource during restart of server with dynamically generated REST WAR file

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2606?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2606: -------------------------------- Fix Version/s: 8.5 > Duplicate resource during restart of server with dynamically generated REST WAR file > ------------------------------------------------------------------------------------ > > Key: TEIID-2606 > URL: https://issues.jboss.org/browse/TEIID-2606 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.1 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.5 > > > I have VDB that is designed to generate the REST WAR file, after the deployment of the VDB, if server is restarted the below error is thrown > {code} > 15:07:26,514 ERROR [org.jboss.as.controller.management-operation] (teiid-async-threads - 4) JBAS014613: Operation ("add") failed - address: ([("deployment" => "sakila_1.war")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"sakila_1.war\")]" > 15:07:26,519 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) Failed to deploy sakila_1.war: org.teiid.adminapi.AdminProcessingException: TEIID70006 {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014803: Duplicate resource [(\"deployment\" => \"sakila_1.war\")]"}} > at org.teiid.adminapi.AdminFactory$AdminImpl.execute(AdminFactory.java:484) [teiid-admin-8.4.1.jar:8.4.1] > at org.teiid.adminapi.AdminFactory$AdminImpl.deploy(AdminFactory.java:749) [teiid-admin-8.4.1.jar:8.4.1] > at org.teiid.jboss.rest.ResteasyEnabler$1.run(ResteasyEnabler.java:94) [teiid-jboss-integration-8.4.1.jar:8.4.1] > at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) > at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:806) > at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45) > at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:847) > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_35] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > {code} -- 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

11 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2013