January 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3146) Billing mechanism based on the query's complexity

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3146?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-3146 at 1/16/15 10:19 AM: ----------------------------------------------------------------- I'm not sure we can provide a turn-key billing mechanism. It's best to concentrate on the underlying parameters and work from there. We have TEIID-3147 - for bytes transferred to the Teiid client The various processing time in the query plan and TEIID-2813 which is applicable to processor threads (although they end up doing some processing work on behalf of other threads in the buffer manager) as well to get the cpu time rather than the wall clock time. We could also look at adding memory batch statistics to the plan - however that can get messy as typically you'd want to correlate to disk usage which is handled lower down and by other threads etc. was (Author: shawkins): I'm not sure we can provide a turn-key billing mechanism. It's best to concentrate on the underlying parameters and work from there. We have TEIID-3146 - for bytes transferred to the Teiid client The various processing time in the query plan and TEIID-2813 which is applicable to processor threads (although they end up doing some processing work on behalf of other threads in the buffer manager) as well to get the cpu time rather than the wall clock time. We could also look at adding memory batch statistics to the plan - however that can get messy as typically you'd want to correlate to disk usage which is handled lower down and by other threads etc. > Billing mechanism based on the query's complexity > ------------------------------------------------- > > Key: TEIID-3146 > URL: https://issues.jboss.org/browse/TEIID-3146 > Project: Teiid > Issue Type: Feature Request > Reporter: Joao Viragine > Assignee: Steven Hawkins > Priority: Minor > Fix For: Open To Community > > > It would be nice if we had a billing mechanism based on the query's complexity. > Teeid exposes information about the queries issued, the amount of records returned, the time elapsed and the query plan. > It could also expose the amount of data (in bytes) returned by each query. > We could combine the above data plus the query complexity to create a score for a billing calculation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3146) Billing mechanism based on the query's complexity

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3146?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-3146: ------------------------------------- Fix Version/s: Open To Community Assignee: (was: Steven Hawkins) > Billing mechanism based on the query's complexity > ------------------------------------------------- > > Key: TEIID-3146 > URL: https://issues.jboss.org/browse/TEIID-3146 > Project: Teiid > Issue Type: Feature Request > Reporter: Joao Viragine > Priority: Minor > Fix For: Open To Community > > > It would be nice if we had a billing mechanism based on the query's complexity. > Teeid exposes information about the queries issued, the amount of records returned, the time elapsed and the query plan. > It could also expose the amount of data (in bytes) returned by each query. > We could combine the above data plus the query complexity to create a score for a billing calculation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3255) Support PicketBox / XACML authorization

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3255?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-3255: ------------------------------------- Fix Version/s: Open To Community Assignee: (was: Steven Hawkins) Yes it was a possible intention of TEIID-1031 to rationalize data roles as XACML. Given that the PolicyDecider is pluggable, do you already have an example implementation that would be possible to contribute? > While this doesn't solve row-based restrictions, it would solve column / object based restrictions. While we put the masking/row specification in the data roles, they are currently handled by an alternative set of logic so they wouldn't be affected if basic policy decisions were handled differently. It also doesn't look like PicketBox supports XACML v3 yet. > Support PicketBox / XACML authorization > --------------------------------------- > > Key: TEIID-3255 > URL: https://issues.jboss.org/browse/TEIID-3255 > Project: Teiid > Issue Type: Feature Request > Components: OData > Affects Versions: 8.9 > Reporter: John Muller > Fix For: Open To Community > > > We would like the OData, OData4, JDBC, and ODBC transports of Teiid to act as an XACML policy enforcement point for all CRUD operations (as well as execute stored procedures). Looking through old JIRAs: > https://issues.jboss.org/browse/TEIID-1031 > it looks like this was considered back in the mid-2010 timeframe, but wasn't fully thought through. With XACML 3.0, it's possible to use Multiple Decision Profile to get all policy decisions for a given user / resource (or just everything for a user for multiple resources). Our idea here is to have Teiid set the action to be one of (SELECT|INSERT|UPDATE|DELETE|CREATE|DROP|EXECUTE) and the resource to be the fully qualified table (vdbName, SchemaName, TableName) plus a map of projected columns by the query. While this doesn't solve row-based restrictions, it would solve column / object based restrictions. MDP could be used to get policy decisions for all objects under a given schema. > Thoughts? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3272) JDBC Translator | Segregation of batch execution and commit mode

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3272?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3272: --------------------------------------- As written we would need to mark this issue as non-resolvable. Do you want to rephrase this issue as an enhancement to allow for the direct usage of source local transactions from a client perspective? > JDBC Translator | Segregation of batch execution and commit mode > ----------------------------------------------------------------- > > Key: TEIID-3272 > URL: https://issues.jboss.org/browse/TEIID-3272 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Shiveeta Mattoo > Assignee: Steven Hawkins > Labels: Batch-Commit, JDBC-Transator > Attachments: batch1.png > > > In JDBC Translator, the batch execution and commit are coupled together. Hence, we after every batch execution, a commit is executed. > This enhancement is for providing an ability to support the commit after a configurable 'x' no. of batches has completed, instead of an automatic commit after every batch. > The no of batches after which a commit is desired should be a configurable option. > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3288) Upgrade JDG DSL querying using hotrod client over protobuffers to JDG 6.4

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3288?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3288: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1183046 > Upgrade JDG DSL querying using hotrod client over protobuffers to JDG 6.4 > ------------------------------------------------------------------------- > > Key: TEIID-3288 > URL: https://issues.jboss.org/browse/TEIID-3288 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.10 > Reporter: Van Halbert > Assignee: Van Halbert > > Upgrade the JDG DSL remote hotrod client over protobuffers from the JDG 6.3 tech preview to JDG 6.4. > This upgrade will allow user to specify what's query able using annotations and will eliminate the dependency protobuf jar. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3288) Upgrade JDG DSL querying using hotrod client over protobuffers to JDG 6.4

by Van Halbert (JIRA)

Van Halbert created TEIID-3288: ---------------------------------- Summary: Upgrade JDG DSL querying using hotrod client over protobuffers to JDG 6.4 Key: TEIID-3288 URL: https://issues.jboss.org/browse/TEIID-3288 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Affects Versions: 8.7.1, 8.10 Reporter: Van Halbert Assignee: Van Halbert Upgrade the JDG DSL remote hotrod client over protobuffers from the JDG 6.3 tech preview to JDG 6.4. This upgrade will allow user to specify what's query able using annotations and will eliminate the dependency protobuf jar. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2816) HBase Connector/Translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2816?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2816: --------------------------------------- > I have started that, do you think we need create a separate HBase translator page or just append it to JDBC translator? It would either go in the JDBC page or under it. We refer to the common import / translator properties in the JDBC page so they need to be logically together. Thanks for creating the data source page. > HBase Connector/Translator > -------------------------- > > Key: TEIID-2816 > URL: https://issues.jboss.org/browse/TEIID-2816 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, JDBC Connector, JDBC Driver > Affects Versions: Open To Community > Reporter: devin pinkston > Assignee: Kylin Soong > Labels: HBase, Translator > Fix For: 8.10 > > > Develop a HBase translator/connector. Potentially using the Phoenix JDBC driver, supports most SQL and handles connections: > https://github.com/forcedotcom/phoenix -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2816) HBase Connector/Translator

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-2816?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-2816: ------------------------------------ > Can you make a first pass at the doc page? I have started that, do you think we need create a separate HBase translator page or just append it to JDBC translator? I have created a Data Sources page as https://docs.jboss.org/author/display/TEIID/Phoenix+Data+Sources > HBase Connector/Translator > -------------------------- > > Key: TEIID-2816 > URL: https://issues.jboss.org/browse/TEIID-2816 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, JDBC Connector, JDBC Driver > Affects Versions: Open To Community > Reporter: devin pinkston > Assignee: Kylin Soong > Labels: HBase, Translator > Fix For: 8.10 > > > Develop a HBase translator/connector. Potentially using the Phoenix JDBC driver, supports most SQL and handles connections: > https://github.com/forcedotcom/phoenix -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3177) Enforce SSL connections over ODBC when Encryption Mode is enabled

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3177?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3177: ------------------------------------------- Bugzilla Update: (was: Perform) Bugzilla References: (was: https://bugzilla.redhat.com/show_bug.cgi?id=1178797) > Enforce SSL connections over ODBC when Encryption Mode is enabled > ----------------------------------------------------------------- > > Key: TEIID-3177 > URL: https://issues.jboss.org/browse/TEIID-3177 > Project: Teiid > Issue Type: Feature Request > Components: ODBC > Affects Versions: 8.8 > Reporter: Cristiano Nicolai > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.9 > > > When connecting via ODBC transport, even if the encryption mode is set to enabled is still possible to establish non ssl connections. This allows clients to connect via insecure method. We would like that the Teiid transport could reject connections if they are not properly set up using SSL transport. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2816) HBase Connector/Translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2816?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2816: --------------------------------------- Sounds good and the pull was committed. So we'll document this as an Hbase solution that utilizes Phoenix with the appropriate supporting docs. Can you make a first pass at the doc page? > HBase Connector/Translator > -------------------------- > > Key: TEIID-2816 > URL: https://issues.jboss.org/browse/TEIID-2816 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, JDBC Connector, JDBC Driver > Affects Versions: Open To Community > Reporter: devin pinkston > Assignee: Kylin Soong > Labels: HBase, Translator > Fix For: 8.10 > > > Develop a HBase translator/connector. Potentially using the Phoenix JDBC driver, supports most SQL and handles connections: > https://github.com/forcedotcom/phoenix -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2015