[JBoss JIRA] (TEIID-3019) Change SYSADMIN.refreshMatViewRow to support a list of rows instead of just one
by Debbie Steigner (JIRA)
Debbie Steigner created TEIID-3019:
--------------------------------------
Summary: Change SYSADMIN.refreshMatViewRow to support a list of rows instead of just one
Key: TEIID-3019
URL: https://issues.jboss.org/browse/TEIID-3019
Project: Teiid
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Server
Reporter: Debbie Steigner
Assignee: Steven Hawkins
Currently SYSADMIN.refreshMatViewRow supports only passing one key value so it will be nice to be able to pass multiple values or array of values for bulk updates.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 8 months
[JBoss JIRA] (TEIID-3017) jpa type mappings need simplified
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3017:
-------------------------------------
Summary: jpa type mappings need simplified
Key: TEIID-3017
URL: https://issues.jboss.org/browse/TEIID-3017
Project: Teiid
Issue Type: Quality Risk
Security Level: Public (Everyone can see)
Components: Misc. Connectors
Affects Versions: 8.4
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.8
There is type mapping logic in the jpa translator that duplicates data type manager logic. It also has several incorrect mappings, such as Byte[] to Blob.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 8 months
[JBoss JIRA] (TEIID-3016) Add headers parameter to invokeHttp
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3016?page=com.atlassian.jira.plugin... ]
Steven Hawkins edited comment on TEIID-3016 at 6/26/14 10:41 AM:
-----------------------------------------------------------------
Added an optional headers parameter that accepts a JSON clob.
invokeHttp(... headers=>jsonObject('application/json' as ContentType))
The jsonObject and jsonArray functions are helpful for this purpose as we look for a jsonObject with primitive or array of primitive values.
This adds an explicit dependency to the engine (for the JSON handling) but avoids adding another third-party dependency - even if something like httpcore would already exist in AS, it would still increase the embedded footprint.
was (Author: shawkins):
Added an optional headers parameter that accepts a JSON clob.
invokeHttp(... header=>jsonObject('application/json' as ContentType))
The jsonObject and jsonArray functions are helpful for this purpose as we look for a jsonObject with primitive or array of primitive values.
This adds an explicit dependency to the engine (for the JSON handling) but avoids adding another third-party dependency - even if something like httpcore would already exist in AS, it would still increase the embedded footprint.
> Add headers parameter to invokeHttp
> -----------------------------------
>
> Key: TEIID-3016
> URL: https://issues.jboss.org/browse/TEIID-3016
> Project: Teiid
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.8
>
>
> There is a need to set common headers, such as content type and accepts. Since there may be other custom values it probably makes sense to do this as a generic parameter as Ramesh suggests:
> call restBDM.invokeHttp(action => 'POST', endpoint => qp, headers=>'ContentType=application/json;Accepts=application/text')
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 8 months
[JBoss JIRA] (TEIID-3016) Add headers parameter to invokeHttp
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3016?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3016.
-----------------------------------
Resolution: Done
Added an optional headers parameter that accepts a JSON clob.
invokeHttp(... header=>jsonObject('application/json' as ContentType))
The jsonObject and jsonArray functions are helpful for this purpose as we look for a jsonObject with primitive or array of primitive values.
This adds an explicit dependency to the engine (for the JSON handling) but avoids adding another third-party dependency - even if something like httpcore would already exist in AS, it would still increase the embedded footprint.
> Add headers parameter to invokeHttp
> -----------------------------------
>
> Key: TEIID-3016
> URL: https://issues.jboss.org/browse/TEIID-3016
> Project: Teiid
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.8
>
>
> There is a need to set common headers, such as content type and accepts. Since there may be other custom values it probably makes sense to do this as a generic parameter as Ramesh suggests:
> call restBDM.invokeHttp(action => 'POST', endpoint => qp, headers=>'ContentType=application/json;Accepts=application/text')
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 8 months
[JBoss JIRA] (TEIID-3016) Add headers parameter to invokeHttp
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3016?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3016:
---------------------------------------
Otherwise it looks like we'll need to add a dependency to httpcore to use the BasicHeaderValueParser logic.
> Add headers parameter to invokeHttp
> -----------------------------------
>
> Key: TEIID-3016
> URL: https://issues.jboss.org/browse/TEIID-3016
> Project: Teiid
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.8
>
>
> There is a need to set common headers, such as content type and accepts. Since there may be other custom values it probably makes sense to do this as a generic parameter as Ramesh suggests:
> call restBDM.invokeHttp(action => 'POST', endpoint => qp, headers=>'ContentType=application/json;Accepts=application/text')
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 8 months
[JBoss JIRA] (TEIID-3013) Add realm authentication to teiid-security
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3013?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-3013.
---------------------------------
Labels: Beta3 (was: )
Resolution: Done
I simply overwrote application-users.properties files in the testing with following line
{code}
user=c5568adea472163dfc00c19c6348a665
{code}
That let the tests pass with previous password.
> Add realm authentication to teiid-security
> ------------------------------------------
>
> Key: TEIID-3013
> URL: https://issues.jboss.org/browse/TEIID-3013
> Project: Teiid
> Issue Type: Quality Risk
> Security Level: Public(Everyone can see)
> Components: Server
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Labels: Beta3
> Fix For: 8.7.1, 8.8
>
>
> To allow teiid to use users added by the console by default we should add the RealmDirect login module to the teiid-security security domain.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 8 months