[JBoss JIRA] (ISPN-8535) Rest API redesign
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-8535?page=com.atlassian.jira.plugin... ]
Gustavo Fernandes closed ISPN-8535.
-----------------------------------
> Rest API redesign
> -----------------
>
> Key: ISPN-8535
> URL: https://issues.redhat.com/browse/ISPN-8535
> Project: Infinispan
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 9.2.0.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> Infinispan REST API deals with only one resource, (the cache) and maps all operations on the cache using HTTP verbs and request parameters. The API assumes the URI is related to the cache making it hard to add new kinds of resources without causing ambiguous references.
> Since we now have other types of entities, such as counters, scripts, templates, etc, and each one of them can involve different operations, we should make the API more "Restful" by using more than one resource and collections of resources, plus HTTP verbs and operations on them. Examples:
> * Create a cache: POST /rest/caches
> * Delete a cache: DELETE /rest/caches/myCache
> * Create a template: POST /rest/templates
> * Delete a template: DELETE /rest/templates/myTemplate
> * Create an entry: POST /rest/caches/myCache/1
> * Create a counter: POST /rest/counters
> * Get a counter value: GET /rest/counters/mycounter
> * Increment a counter: GET /rest/counters/mycounter?action=increment
> * Search a cache: GET /rest/caches/myCache?action=search
> * Create a script: POST /rest/scripts/
> * Get a script source: GET /rest/scritps/myScript
> * Execute a script: GET /rest/scripts/myScript?action=execute¶m1=foo
> * Stop individual servers and the full cluster
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (ISPN-8535) Rest API redesign
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-8535?page=com.atlassian.jira.plugin... ]
Gustavo Fernandes updated ISPN-8535:
------------------------------------
Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #30, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #30, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39)
> Rest API redesign
> -----------------
>
> Key: ISPN-8535
> URL: https://issues.redhat.com/browse/ISPN-8535
> Project: Infinispan
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 9.2.0.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> Infinispan REST API deals with only one resource, (the cache) and maps all operations on the cache using HTTP verbs and request parameters. The API assumes the URI is related to the cache making it hard to add new kinds of resources without causing ambiguous references.
> Since we now have other types of entities, such as counters, scripts, templates, etc, and each one of them can involve different operations, we should make the API more "Restful" by using more than one resource and collections of resources, plus HTTP verbs and operations on them. Examples:
> * Create a cache: POST /rest/caches
> * Delete a cache: DELETE /rest/caches/myCache
> * Create a template: POST /rest/templates
> * Delete a template: DELETE /rest/templates/myTemplate
> * Create an entry: POST /rest/caches/myCache/1
> * Create a counter: POST /rest/counters
> * Get a counter value: GET /rest/counters/mycounter
> * Increment a counter: GET /rest/counters/mycounter?action=increment
> * Search a cache: GET /rest/caches/myCache?action=search
> * Create a script: POST /rest/scripts/
> * Get a script source: GET /rest/scritps/myScript
> * Execute a script: GET /rest/scripts/myScript?action=execute¶m1=foo
> * Stop individual servers and the full cluster
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (ISPN-10435) Support for serving static content
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-10435?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-10435:
-------------------------------------
Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39)
> Support for serving static content
> ----------------------------------
>
> Key: ISPN-10435
> URL: https://issues.redhat.com/browse/ISPN-10435
> Project: Infinispan
> Issue Type: Feature Request
> Components: REST
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
> Labels: console-ng
> Fix For: 10.0.0.CR2
>
>
> The REST endpoint should be able to serve the console from a static folder, respecting usual http headers sent by browsers to facilitate caching such as if-modified-since
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (ISPN-11166) SocketTimeoutFailureRetryTest random failures
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-11166?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-11166:
------------------------------------------
Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38)
> SocketTimeoutFailureRetryTest random failures
> ---------------------------------------------
>
> Key: ISPN-11166
> URL: https://issues.redhat.com/browse/ISPN-11166
> Project: Infinispan
> Issue Type: Bug
> Components: Server, Test Suite
> Affects Versions: 10.1.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Labels: testsuite_stability
> Fix For: 11.0.0.Final
>
>
> Replicated non-tx caches without stores have an optimization for get operations to bypass the interceptor chain and query the data container directly. The optimization was added with the non-blocking listener changes, in order to compensate their overhead, but it only covered {{get()}} and {{getAsync()}}, while the HotRod server uses {{getCacheEntryAsync()}}.
> The ISPN-11020 fix extended the replicated get optimization to {{getCacheEntryAsync()}}, so now HotRod replicated reads bypass the interceptor chain, including the {{DelayingInterceptor}} added by {{SocketTimeoutFailureRetryTest}}.
> {noformat}
> java.lang.AssertionError: expected:<1> but was:<0>
> at org.testng.AssertJUnit.fail(AssertJUnit.java:59)
> at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:170)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:177)
> at org.infinispan.client.hotrod.retry.SocketTimeoutFailureRetryTest.testRetrySocketTimeout(SocketTimeoutFailureRetryTest.java:68)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (ISPN-11168) DuplicateDomainCdiIT should use manifest dependencies
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-11168?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-11168:
------------------------------------------
Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38)
> DuplicateDomainCdiIT should use manifest dependencies
> -----------------------------------------------------
>
> Key: ISPN-11168
> URL: https://issues.redhat.com/browse/ISPN-11168
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite, WildFly modules
> Affects Versions: 10.1.0.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.1.2.Final
>
>
> DuplicateDomainCdiIT currently pulls in dependencies through Shrinkwrap's pom resolution. This is quite brittle in some environments. The test should be changed to use wildfly manifest dependencies.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (ISPN-11148) CLI hangs on exit after connection failure
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-11148?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-11148:
------------------------------------------
Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38)
> CLI hangs on exit after connection failure
> ------------------------------------------
>
> Key: ISPN-11148
> URL: https://issues.redhat.com/browse/ISPN-11148
> Project: Infinispan
> Issue Type: Bug
> Components: CLI
> Affects Versions: 10.1.0.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.1.1.Final
>
>
> Whenever the CLI fails to connect to the server, it will hang on exit. This also happens when attempting to connect to a server with authentication without providing credentials on the connection command.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months