[JBoss JIRA] Created: (TEIID-1055) Secure profile service access
by Ramesh Reddy (JIRA)
Secure profile service access
-----------------------------
Key: TEIID-1055
URL: https://jira.jboss.org/jira/browse/TEIID-1055
Project: Teiid
Issue Type: Task
Components: AdminApi
Affects Versions: 7.0
Reporter: Ramesh Reddy
Fix For: 7.0
As of 7.0 M3 release, the "Profile Service" access is not secure. Currently the JOPR plug-in and Teiid Admin API, force users to authenticate with "jmx-console" security domain, both these do not prevent the direct access to the "Profile Service" EJB directly.
Profile Service can be deployed as secure EJB, such that it would require a login context to be authenticated before user has access to this bean. This needs to be configured and tested. Also document, how to configure the profile service as secure service.
Also, AdminFactory class, which provides Admin connections, need to work with secure "Profile Service".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (TEIID-829) revamp code table caching
by Steven Hawkins (JIRA)
revamp code table caching
-------------------------
Key: TEIID-829
URL: https://jira.jboss.org/jira/browse/TEIID-829
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 6.3.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 6.3.0
Code tables have several design issues:
1. the cache should allow for eviction and possibly expiration.
2. the cache should be backed by the common caching facility.
3. should allow for explicit scoping - at a minimum global vs. vdb, but additional may be good to allow session and request.
4. the implementation should be minimally blocking (in terms of both query execution and use of synchronization).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (TEIID-892) Add a capability to control bulk insert batch size
by Steven Hawkins (JIRA)
Add a capability to control bulk insert batch size
--------------------------------------------------
Key: TEIID-892
URL: https://jira.jboss.org/jira/browse/TEIID-892
Project: Teiid
Issue Type: Feature Request
Components: Connector API, Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 7.0
Based upon a recent customer conversation our default batching strategy to the connector may not be the most performant for large datasets. In general our current approach limits batches to a maximum = processor batch size (default 2000).
We already have a property connector batch size, but it's across all connectors - and is mostly irrelevant since the source fetch size will have a larger impact on performance and the result batches are resized to the processor batch size anyway. The only time connector batch size really matters is if we bring back "remote" connectors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months