[JBoss JIRA] (TEIID-4533) Change the default max-staleness for the resultset cache to 0
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-4533:
-------------------------------------
Summary: Change the default max-staleness for the resultset cache to 0
Key: TEIID-4533
URL: https://issues.jboss.org/browse/TEIID-4533
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine, Server
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 9.2
We have inherited the property setting for years and have to call it out in several places in the docs. It would be best to default to 0, and instead call out in the docs that cache can be made more tolerant to stale entries.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months
[JBoss JIRA] (TEIID-4366) Provide CORS support on OData Service
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4366?page=com.atlassian.jira.plugin... ]
Ramesh Reddy edited comment on TEIID-4366 at 10/21/16 11:14 AM:
----------------------------------------------------------------
[~jdurani] and [~jolee] I found in my testing that SDK's _HttpURLConnection_ blocks the setting of the ORIGIN header, thus the issue you report. I think even the CXF HttpClient deep underneath also uses _HttpURLConnection_ The test needs to avoid using this class, I have not spent time figuring out how to do that in JAVA, may be you can try CURL or some perl/python script? As you see above in one of the comments, I used the anjular.js java script for testing.
was (Author: rareddy):
[~jdurani] and [~jolee] I found in my testing that SDK's _HttpURLConnection _ blocks the setting of the ORIGIN header, thus the issue you report. I think even the CXF HttpClient deep underneath also uses _HttpURLConnection_ The test needs to avoid using this class, I have not spent time figuring out how to do that in JAVA, may be you can try CURL or some perl/python script? As you see above in one of the comments, I used the anjular.js java script for testing.
> Provide CORS support on OData Service
> -------------------------------------
>
> Key: TEIID-4366
> URL: https://issues.jboss.org/browse/TEIID-4366
> Project: Teiid
> Issue Type: Enhancement
> Components: OData
> Affects Versions: 8.12
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Labels: Alpha3
> Fix For: 9.1, 9.0.4, 8.12.7.6_3
>
>
> Good write up CORS can be found here https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS
> OData needs to implement CORS support to be valuable with java script based client development technologies.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months
[JBoss JIRA] (TEIID-4366) Provide CORS support on OData Service
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4366?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4366:
-------------------------------------
[~jdurani] and [~jolee] I found in my testing that SDK's _HttpURLConnection _ blocks the setting of the ORIGIN header, thus the issue you report. I think even the CXF HttpClient deep underneath also uses _HttpURLConnection_ The test needs to avoid using this class, I have not spent time figuring out how to do that in JAVA, may be you can try CURL or some perl/python script? As you see above in one of the comments, I used the anjular.js java script for testing.
> Provide CORS support on OData Service
> -------------------------------------
>
> Key: TEIID-4366
> URL: https://issues.jboss.org/browse/TEIID-4366
> Project: Teiid
> Issue Type: Enhancement
> Components: OData
> Affects Versions: 8.12
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Labels: Alpha3
> Fix For: 9.1, 9.0.4, 8.12.7.6_3
>
>
> Good write up CORS can be found here https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS
> OData needs to implement CORS support to be valuable with java script based client development technologies.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months
[JBoss JIRA] (TEIID-2578) add/remove schema elements
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2578:
---------------------------------------
I'll take another pass through as I made the refactoring to DatabaseStore/Storage without considering the remote nature of the service. In general the problem we have is that the locking is based upon a single vm, and can then would call into a shared service potentially with competing state.
> add/remove schema elements
> --------------------------
>
> Key: TEIID-2578
> URL: https://issues.jboss.org/browse/TEIID-2578
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 9.2
>
>
> Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months