July 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3493) Use certificates in Salesforce SOAP API calls

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3493?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-3493: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Use certificates in Salesforce SOAP API calls > --------------------------------------------- > > Key: TEIID-3493 > URL: https://issues.jboss.org/browse/TEIID-3493 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Reporter: Burak Serdar > Assignee: Ramesh Reddy > Fix For: 8.12 > > > Currently salesforce connector supports user/password authentication. It would be nice if we can use certificates. > https://help.salesforce.com/apex/HTViewHelpDoc?id=security_keys_uploading... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3602) NU.XOM dependency not defined for XOM for EAP Kit

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3602?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3602: ------------------------------------- Originated with https://issues.jboss.org/browse/TEIID-3371 > NU.XOM dependency not defined for XOM for EAP Kit > ------------------------------------------------- > > Key: TEIID-3602 > URL: https://issues.jboss.org/browse/TEIID-3602 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.11 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.12, 8.11.2 > > > There is regression in defining the NU.XOM dependency on XOM.XOM module. It is been defined in Teiid's module, but not in XOM.XOM -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3602) NU.XOM dependency not defined for XOM for EAP Kit

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3602: ----------------------------------- Summary: NU.XOM dependency not defined for XOM for EAP Kit Key: TEIID-3602 URL: https://issues.jboss.org/browse/TEIID-3602 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.11 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.12, 8.11.2 There is regression in defining the NU.XOM dependency on XOM.XOM module. It is been defined in Teiid's module, but not in XOM.XOM -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3594) Change the default for command logging to write User query (start/end)

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3594?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3594: ------------------------------------- Got it thanks. > Change the default for command logging to write User query (start/end) > ---------------------------------------------------------------------- > > Key: TEIID-3594 > URL: https://issues.jboss.org/browse/TEIID-3594 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Van Halbert > Assignee: Steven Hawkins > > The command logging currently writes the user query and the source queries. Would like to have multiple levels for command logging, example: > - default, log the user query start and end entry > - debug, log the use query and the source queries -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3493) Use certificates in Salesforce SOAP API calls

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3493?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3493: ------------------------------------- [~bserdar] [~jorge.herrera] I have this available with CXF to configure the certificate, but have no way to test it, is there anyway you can help test this? > Use certificates in Salesforce SOAP API calls > --------------------------------------------- > > Key: TEIID-3493 > URL: https://issues.jboss.org/browse/TEIID-3493 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Reporter: Burak Serdar > Assignee: Steven Hawkins > Fix For: 8.12 > > > Currently salesforce connector supports user/password authentication. It would be nice if we can use certificates. > https://help.salesforce.com/apex/HTViewHelpDoc?id=security_keys_uploading... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3594) Change the default for command logging to write User query (start/end)

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3594?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3594: --------------------------------------- Current: Overall teiid context at INFO Command logs all to DEBUG Proposed: Overall teiid context at INFO Command log context at WARN User command logs to INFO level Source command logs to DEBUG level This is the least backwards compatibility issues. As the other way would require putting the source commands at the trace level, which would also be the level that the query plan is logged at. > Change the default for command logging to write User query (start/end) > ---------------------------------------------------------------------- > > Key: TEIID-3594 > URL: https://issues.jboss.org/browse/TEIID-3594 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Van Halbert > Assignee: Steven Hawkins > > The command logging currently writes the user query and the source queries. Would like to have multiple levels for command logging, example: > - default, log the user query start and end entry > - debug, log the use query and the source queries -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3594) Change the default for command logging to write User query (start/end)

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3594?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3594: ------------------------------------- yes, that is simpler. Having the context in logging or not defines the logging. Level defines the level. Perfect. You mean INFO and DEBUG, right now we are at DEBUG > Change the default for command logging to write User query (start/end) > ---------------------------------------------------------------------- > > Key: TEIID-3594 > URL: https://issues.jboss.org/browse/TEIID-3594 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Van Halbert > Assignee: Steven Hawkins > > The command logging currently writes the user query and the source queries. Would like to have multiple levels for command logging, example: > - default, log the user query start and end entry > - debug, log the use query and the source queries -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3591) Report user query CPU time

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3591?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3591: --------------------------------------- > Should a corresponding TEIID-RHQ jira be logged so that this info is exposed when using JON? Sounds fine to me. As for what we report for the cpu time, the simplest cut would just include the timing around request work item. That does not include all of time associated with IO work nor with minor things such as more work tasks. With a little extra work I'd be able to include the times from asynch tasks in xmltable and texttable (although it is possible, but not expected that those could run in the submitting thread) and remove any duplicate time associated with serial connector work. > Report user query CPU time > -------------------------- > > Key: TEIID-3591 > URL: https://issues.jboss.org/browse/TEIID-3591 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.12 > > > Just like TEIID-2813 it would useful to be useful to report CPU time for user query overall. This can help determine load on CPU got given user query vs wait time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3594) Change the default for command logging to write User query (start/end)

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3594?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3594: --------------------------------------- It does seem simpler rethinking this to just break out the command logging context by default in the configuration. Then we can default it to a warn level rather than info and not add another configuration property. > Change the default for command logging to write User query (start/end) > ---------------------------------------------------------------------- > > Key: TEIID-3594 > URL: https://issues.jboss.org/browse/TEIID-3594 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Van Halbert > Assignee: Steven Hawkins > > The command logging currently writes the user query and the source queries. Would like to have multiple levels for command logging, example: > - default, log the user query start and end entry > - debug, log the use query and the source queries -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3594) Change the default for command logging to write User query (start/end)

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3594?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3594: ------------------------------------- - We got to find a solution where restart is not needed, otherwise it is bigger issue turning on running servers. > Can you elaborate on what you mean by this? Right now we turn or off the commend logging, with use of logging context, and as well as logging level, if we introduce another flag it should take over the notion of the logging level for entire command/audit logging, user should not be modifying yet another property. This way we can configure appenders for the command/audit logging by default, then just control the logging the message or not. > Change the default for command logging to write User query (start/end) > ---------------------------------------------------------------------- > > Key: TEIID-3594 > URL: https://issues.jboss.org/browse/TEIID-3594 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Van Halbert > Assignee: Steven Hawkins > > The command logging currently writes the user query and the source queries. Would like to have multiple levels for command logging, example: > - default, log the user query start and end entry > - debug, log the use query and the source queries -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2015