[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, 4 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, 4 months
[JBoss JIRA] Created: (TEIID-1162) Document the recommended approach to using entitlements
by Van Halbert (JIRA)
Document the recommended approach to using entitlements
-------------------------------------------------------
Key: TEIID-1162
URL: https://jira.jboss.org/browse/TEIID-1162
Project: Teiid
Issue Type: Task
Components: Documentation
Reporter: Van Halbert
Assignee: Steve Hawkins
Priority: Blocker
Document the recommended approach to using entitlements and indicate what happens when permissions are applied to a Virtual Layer for which the underlying (virtual) model already has entitlements assigned. Any concerns, regarding how data might be accidentally exposed, should be highlighted. Yes, we say an experienced person should be the one responsible for security, but we must also provide direction to this person in order that they be successful.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (TEIID-1175) SqlServer 2005 - Queries failing due to negative values being treated as positive values
by Warren Gibson (JIRA)
SqlServer 2005 - Queries failing due to negative values being treated as positive values
----------------------------------------------------------------------------------------
Key: TEIID-1175
URL: https://jira.jboss.org/browse/TEIID-1175
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.1
Reporter: Warren Gibson
Assignee: Steve Hawkins
It appears results are being returned without consideration for the negative(-) sign
- RDBMS_Test_Queries_1000_TestQuery169
SELECT SmallA.IntKey FROM SmallA WHERE SmallA.StringNum > 11 AND SmallA.StringNum < 15 ORDER BY IntKey
Query suite is expecting 3 rows returned.
Query results straight to source returns:
36
37
38
Query results from Teiid:
10
11
12
13
36
37
38
Source contains the following for IntKey and StringNum
IntKey StringNum
0 -24
1 <null>
2 -22
3 -21
4 -20
5 -19
6 -18
7 -17
8 -16
9 -15
10 -14
11 -13
12 -12
13 -11
14 -10
15 -9
16 -8
17 <null>
18 -6
19 -5
20 -4
21 -3
22 -2
23 -1
24 0
25 1
26 2
27 3
28 4
29 5
30 6
31 7
32 8
33 <null>
34 10
35 11
36 12
37 13
38 14
39 15
40 16
41 17
42 18
43 19
44 20
45 21
46 22
47 23
48 24
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (TEIID-1153) Turned of ProfileService authenticatiion and it caused an NPE in the Teiid RHQ Plugin
by Van Halbert (JIRA)
Turned of ProfileService authenticatiion and it caused an NPE in the Teiid RHQ Plugin
-------------------------------------------------------------------------------------
Key: TEIID-1153
URL: https://jira.jboss.org/browse/TEIID-1153
Project: Teiid
Issue Type: Bug
Components: Jopr Plugin
Environment: SOA-P
Reporter: Van Halbert
Assignee: Steve Hawkins
Turned of ProfileService authenticatiion and it caused an NPE in the Teiid RHQ Plugin,
Exception:
java.lang.Exception: Discovery component invocation failed.
at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:270)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:637)
Caused by: java.lang.NullPointerException
at org.teiid.rhq.plugin.util.ProfileServiceUtil.getSimpleValue(ProfileServiceUtil.java:296)
at org.teiid.rhq.plugin.PlatformDiscoveryComponent.discoverResources(PlatformDiscoveryComponent.java:66)
at sun.reflect.GeneratedMethodAccessor339.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:266)
... 5 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months