April 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2432) Dynamic VDB isLoading state doesnt change on fail

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2432?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2432: --------------------------------------- The field will likely be called MetadataStatus. How about the values LOADING, LOADED, FAILED, RETRYING > Dynamic VDB isLoading state doesnt change on fail > ------------------------------------------------- > > Key: TEIID-2432 > URL: https://issues.jboss.org/browse/TEIID-2432 > Project: Teiid > Issue Type: Feature Request > Components: AdminApi > Affects Versions: 8.2 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Fix For: 8.4 > > > I am deploying a dynamic VDB and polling the isLoading state to determine when the VDB deployment is finished. > In my case the VDB dataSource is not available. I can see in the server log that the deployment fails immediately, but the isLoading state remains true. > Is this in error, or what status should we be checking? -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2444) Teiid should be deployable in EAP 6.1 bits

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2444?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2444. --------------------------------- Labels: alpha1 (was: ) Resolution: Done All the configuration is updated and usage of deprecated API has been removed from Teiid Subsystem extension modules. > Teiid should be deployable in EAP 6.1 bits > ------------------------------------------ > > Key: TEIID-2444 > URL: https://issues.jboss.org/browse/TEIID-2444 > Project: Teiid > Issue Type: Task > Components: Build/Kits, Server > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Labels: alpha1 > Fix For: 8.4 > > > EAP 6.1 Alpha 1 is available in community, Teiid must be able to layered on top of this version to make use this version. > EAP 6.1 alpaha1, fixes few major issues that were discovered on AS 7.1.1 version. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2432) Dynamic VDB isLoading state doesnt change on fail

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2432?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2432: -------------------------------- Fix Version/s: 8.4 Affects: Documentation (Ref Guide, User Guide, etc.) So what do call this 4th state? * METADATA_LOAD_FAILED * DATA_SOURCE_ERROR * ? > Dynamic VDB isLoading state doesnt change on fail > ------------------------------------------------- > > Key: TEIID-2432 > URL: https://issues.jboss.org/browse/TEIID-2432 > Project: Teiid > Issue Type: Feature Request > Components: AdminApi > Affects Versions: 8.2 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Fix For: 8.4 > > > I am deploying a dynamic VDB and polling the isLoading state to determine when the VDB deployment is finished. > In my case the VDB dataSource is not available. I can see in the server log that the deployment fails immediately, but the isLoading state remains true. > Is this in error, or what status should we be checking? -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2326) Allow importing vdbs to share the materialized view of imported vdbs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2326?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2326: --------------------------------------- There isn't an easy way to restrict that. For simplicity I'll probably just add something similar to the VDBImport importDataPolicies. > Allow importing vdbs to share the materialized view of imported vdbs > -------------------------------------------------------------------- > > Key: TEIID-2326 > URL: https://issues.jboss.org/browse/TEIID-2326 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4 > > > Currently the end importing vdb will be the owner of a distinct set of internal materialized views regardless of whether those materialized views come from an imported vdb. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2326) Allow importing vdbs to share the materialized view of imported vdbs

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2326?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIID-2326 at 4/3/13 8:32 AM: ------------------------------------------------------------- How about restricting the use of the system tables in materialized views to only top level vdbs? was (Author: rareddy): How about restricting the use of the system tables to only top level vdbs? > Allow importing vdbs to share the materialized view of imported vdbs > -------------------------------------------------------------------- > > Key: TEIID-2326 > URL: https://issues.jboss.org/browse/TEIID-2326 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4 > > > Currently the end importing vdb will be the owner of a distinct set of internal materialized views regardless of whether those materialized views come from an imported vdb. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2326) Allow importing vdbs to share the materialized view of imported vdbs

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2326?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2326: ------------------------------------- How about restricting the use of the system tables to only top level vdbs? > Allow importing vdbs to share the materialized view of imported vdbs > -------------------------------------------------------------------- > > Key: TEIID-2326 > URL: https://issues.jboss.org/browse/TEIID-2326 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4 > > > Currently the end importing vdb will be the owner of a distinct set of internal materialized views regardless of whether those materialized views come from an imported vdb. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2381) Expanded source hint support

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2381?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2381: --------------------------------------- Vineela, it would help more to describe your scenarios based upon bullets that I have outlined above. What you are getting at I believe is the last bullet - that is you want to expand upon the usage of the hint in view layers (which is currently documented as limited to simple query scenarios only). In this case, what do you propose to do when a source hint appears a multiple levels of the query (concat hints, top overrides, etc.) How does the optimization process affect the interpretation of a source hint in a view or multiple locations in a user query - for example when placed within a subquery that is optimized to a join or a flattened view layer? Do you have any thoughts as to the other bullets: Do you need something akin to global syntax support to specify where a source hint is applicable? Do you need the hint to appear in alternative locations in the source sql? > Expanded source hint support > ---------------------------- > > Key: TEIID-2381 > URL: https://issues.jboss.org/browse/TEIID-2381 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Attachments: HintsExecutionFactory.java, RandomExecutionFactory.java, RandomNumberStoredProcedureExecution.java, SysviewHintsExecutionTest.java > > > We currently look at the source hint in only the root user query (not in subqueries nor the with clause) and only consider it in a very narrow set of circumstances when it's used in a view. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2381) Expanded source hint support

by Vineela Gampa (JIRA)

[ https://issues.jboss.org/browse/TEIID-2381?page=com.atlassian.jira.plugin... ] Vineela Gampa updated TEIID-2381: --------------------------------- Attachment: SysviewHintsExecutionTest.java HintsExecutionFactory.java RandomExecutionFactory.java RandomNumberStoredProcedureExecution.java Files for union case > Expanded source hint support > ---------------------------- > > Key: TEIID-2381 > URL: https://issues.jboss.org/browse/TEIID-2381 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Attachments: HintsExecutionFactory.java, RandomExecutionFactory.java, RandomNumberStoredProcedureExecution.java, SysviewHintsExecutionTest.java > > > We currently look at the source hint in only the root user query (not in subqueries nor the with clause) and only consider it in a very narrow set of circumstances when it's used in a view. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2381) Expanded source hint support

by Vineela Gampa (JIRA)

[ https://issues.jboss.org/browse/TEIID-2381?page=com.atlassian.jira.plugin... ] Vineela Gampa commented on TEIID-2381: -------------------------------------- Another usecase We observed that teiid hints are lot when the query is unioned.hintsexec.random_hintsview is a view which has sourcehint and general hint in its tranformation query. when we execute select * we see hints getting passed , but when unioned with something hints are lost. Please find the attached testcase. Below is the output from the unittest. Unit test can be found in com.ca.chorus.server.translator.hints.SysviewHintsExecutionTest.testTeiidHintsDuringUnion() . transformation is SELECT /*+ sh:'general_hint' random:'source_hint' */ random_number FROM (CALL random.random_number(3)) AS b 1 [DEBUG] CHORUS-QUERY - select * from hintsexec.random_hintsview GeneralHint ** general_hint getSourceHint ** source_hint 275 [DEBUG] CHORUS-QUERY - select * from hintsexec.random_hintsview GeneralHint ** general_hint getSourceHint ** source_hint 277 [DEBUG] CHORUS-QUERY - select * from hintsexec.random_hintsview union select 0 GeneralHint ** null getSourceHint ** null > Expanded source hint support > ---------------------------- > > Key: TEIID-2381 > URL: https://issues.jboss.org/browse/TEIID-2381 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > We currently look at the source hint in only the root user query (not in subqueries nor the with clause) and only consider it in a very narrow set of circumstances when it's used in a view. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1979) The RAR should be unbundled when packaged in the jboss kit

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-1979?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-1979. --------------------------------- Labels: Alpha1 (was: ) Resolution: Done All the built in resource adapters are now deployed by default as modules. They also get shorter names, like file, webservice, ldap, salesforce, google, infinispan. The previous mechanisms to use the .rar still exists, the Admin API is corrected to make use of this feature. > The RAR should be unbundled when packaged in the jboss kit > ---------------------------------------------------------- > > Key: TEIID-1979 > URL: https://issues.jboss.org/browse/TEIID-1979 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Van Halbert > Assignee: Ramesh Reddy > Labels: Alpha1 > Fix For: 8.4 > > > The RAR file should be unbundled, instead of zipped up, when it is packaged in the jboss kit. This change is being pushed up stream. -- 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, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2013