November 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5553) Server logging when waiting for metadata loads

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5553?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5553: ---------------------------------- Fix Version/s: (was: 12.0) > Server logging when waiting for metadata loads > ---------------------------------------------- > > Key: TEIID-5553 > URL: https://issues.jboss.org/browse/TEIID-5553 > Project: Teiid > Issue Type: Enhancement > Reporter: Chandra Akkinepalli > Assignee: Steven Hawkins > Priority: Major > > I would like to request better logging in cases when a VDB is waiting on LOADING of another dependent vdbs. Currently there is no messaging around what it is waiting on. > Also another variant of this wait happens when base vdb version is changed and deployed. The importing VDB waits for metadata perpetually. > It would be great to have better logging around metadata logging, something like what metadata is VDB waiting on for deployment would help in debugging any issues. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5553) Server logging when waiting for metadata loads

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5553?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5553. ----------------------------------- Resolution: Duplicate I double checked that the log occurs on initial and reload due to an import reloading. There is no further periodic logging. This can be reopened if something additional is needed, otherwise resolving as a duplicate. > Server logging when waiting for metadata loads > ---------------------------------------------- > > Key: TEIID-5553 > URL: https://issues.jboss.org/browse/TEIID-5553 > Project: Teiid > Issue Type: Enhancement > Reporter: Chandra Akkinepalli > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0 > > > I would like to request better logging in cases when a VDB is waiting on LOADING of another dependent vdbs. Currently there is no messaging around what it is waiting on. > Also another variant of this wait happens when base vdb version is changed and deployed. The importing VDB waits for metadata perpetually. > It would be great to have better logging around metadata logging, something like what metadata is VDB waiting on for deployment would help in debugging any issues. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5553) Server logging when waiting for metadata loads

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5553?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5553: --------------------------------------- > Currently there is no messaging around what it is waiting on. That is satisfied by TEIID-4925. I'll need to check what happens in the specific case of having the imported vdb redployed - the way things look now it probably won't output new messages. > Server logging when waiting for metadata loads > ---------------------------------------------- > > Key: TEIID-5553 > URL: https://issues.jboss.org/browse/TEIID-5553 > Project: Teiid > Issue Type: Enhancement > Reporter: Chandra Akkinepalli > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0 > > > I would like to request better logging in cases when a VDB is waiting on LOADING of another dependent vdbs. Currently there is no messaging around what it is waiting on. > Also another variant of this wait happens when base vdb version is changed and deployed. The importing VDB waits for metadata perpetually. > It would be great to have better logging around metadata logging, something like what metadata is VDB waiting on for deployment would help in debugging any issues. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5553) Server logging when waiting for metadata loads

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5553?page=com.atlassian.jira.plugin... ] Work on TEIID-5553 started by Steven Hawkins. --------------------------------------------- > Server logging when waiting for metadata loads > ---------------------------------------------- > > Key: TEIID-5553 > URL: https://issues.jboss.org/browse/TEIID-5553 > Project: Teiid > Issue Type: Enhancement > Reporter: Chandra Akkinepalli > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0 > > > I would like to request better logging in cases when a VDB is waiting on LOADING of another dependent vdbs. Currently there is no messaging around what it is waiting on. > Also another variant of this wait happens when base vdb version is changed and deployed. The importing VDB waits for metadata perpetually. > It would be great to have better logging around metadata logging, something like what metadata is VDB waiting on for deployment would help in debugging any issues. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5551) Inconsistency with document projection

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5551?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5551. ----------------------------------- Resolution: Done > Inconsistency with document projection > -------------------------------------- > > Key: TEIID-5551 > URL: https://issues.jboss.org/browse/TEIID-5551 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0, 11.2.1 > > > When using the xml type for a given column the entire subtree is returned - which is universally the expected behavior. If projection is used and another type is used, then only local node text will be considered. If projection is disabled, all of the descendant text is considered. > Based upon our initial consistency with oracle, we should consider all of the descendant text. > for example: > Select * From XmlTable('/root' Passing xmlparse(document '<root><def><test1>10</test1><test1>20</test1></def><abc>22</abc></root>') > Columns b varchar(40) Path 'def') xx > should return 1020. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5553) Server logging when waiting for metadata loads

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5553?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5553: ---------------------------------- Fix Version/s: 12.0 > Server logging when waiting for metadata loads > ---------------------------------------------- > > Key: TEIID-5553 > URL: https://issues.jboss.org/browse/TEIID-5553 > Project: Teiid > Issue Type: Enhancement > Reporter: Chandra Akkinepalli > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0 > > > I would like to request better logging in cases when a VDB is waiting on LOADING of another dependent vdbs. Currently there is no messaging around what it is waiting on. > Also another variant of this wait happens when base vdb version is changed and deployed. The importing VDB waits for metadata perpetually. > It would be great to have better logging around metadata logging, something like what metadata is VDB waiting on for deployment would help in debugging any issues. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5538) Option nocache does not apply to subqueries

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5538?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5538. ----------------------------------- Resolution: Done Updated the planner to use the same hint merge logic as through view layers with subqueries. > Option nocache does not apply to subqueries > ------------------------------------------- > > Key: TEIID-5538 > URL: https://issues.jboss.org/browse/TEIID-5538 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0 > > > When specifying "option nocache" or a related option, those hints are only propagated through view layers - but not to sub-queries. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5552) Audit Logging for ODBC

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5552?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5552. ----------------------------------- Resolution: Rejected Unfortunately there's not a great solution here. The teiid JDBC client is responsible for providing a client reported ip. That is not provided by pg clients. > Audit Logging for ODBC > ----------------------- > > Key: TEIID-5552 > URL: https://issues.jboss.org/browse/TEIID-5552 > Project: Teiid > Issue Type: Enhancement > Reporter: Chandra Akkinepalli > Assignee: Steven Hawkins > Priority: Major > > The teiid audit logging for ODBC transport type doesn't log the ip address/ server name of the client when there is load balancer handling the routing to the nodes. > It prints the ip address of the load balancer. > I would like to request to enhanced logging to provide the ip address of the client like JDBC transport. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5552) Audit Logging for ODBC

by Chandra Akkinepalli (Jira)

[ https://issues.jboss.org/browse/TEIID-5552?page=com.atlassian.jira.plugin... ] Chandra Akkinepalli updated TEIID-5552: --------------------------------------- Description: The teiid audit logging for ODBC transport type doesn't log the ip address/ server name of the client when there is load balancer handling the routing to the nodes. It prints the ip address of the load balancer. I would like to request to enhanced logging to provide the ip address of the client like JDBC transport. was: The teiid audit logging for ODBC transport type doesn't log the ip address/ server name of the client when there is load balancer handling the routing to the nodes. It prints the ip address of the load balancer. I would like to request to enhanced logging to provide the ip address of the client like JDBC transport. These details are available via adminshell getSessions() command , but not available in teiid-audit logs. > Audit Logging for ODBC > ----------------------- > > Key: TEIID-5552 > URL: https://issues.jboss.org/browse/TEIID-5552 > Project: Teiid > Issue Type: Enhancement > Reporter: Chandra Akkinepalli > Assignee: Steven Hawkins > Priority: Major > > The teiid audit logging for ODBC transport type doesn't log the ip address/ server name of the client when there is load balancer handling the routing to the nodes. > It prints the ip address of the load balancer. > I would like to request to enhanced logging to provide the ip address of the client like JDBC transport. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5553) Server logging when waiting for metadata loads

by Chandra Akkinepalli (Jira)

Chandra Akkinepalli created TEIID-5553: ------------------------------------------ Summary: Server logging when waiting for metadata loads Key: TEIID-5553 URL: https://issues.jboss.org/browse/TEIID-5553 Project: Teiid Issue Type: Enhancement Reporter: Chandra Akkinepalli Assignee: Steven Hawkins I would like to request better logging in cases when a VDB is waiting on LOADING of another dependent vdbs. Currently there is no messaging around what it is waiting on. Also another variant of this wait happens when base vdb version is changed and deployed. The importing VDB waits for metadata perpetually. It would be great to have better logging around metadata logging, something like what metadata is VDB waiting on for deployment would help in debugging any issues. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2018