[ 
https://issues.apache.org/jira/browse/GEODE-7938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17078369#comment-17078369
 ] 

ASF subversion and git services commented on GEODE-7938:
--------------------------------------------------------

Commit 6263f1f9a4782433d013c6b759bda8c84216b595 in geode's branch 
refs/heads/develop from Darrel Schneider
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=6263f1f ]

GEODE-7938: added keys query param to GET, PUT, and DELETE /{region} endpoints 
(#4901)

* added keys query param to GET, PUT, and DELETE /{region} endpoints
* when getting multiple keys, results are now ordered as the request was ordered
* the code that tests for missing keys now uses the getAll result instead of 
sending multiple messages and having a race in which key is deleted after the 
old check but before getAll
* Added endpoint for PUT {region}?keys=encodedKey&op=CREATE. The CREATE is a 
new op.
This allows users to create entries that have an encodedKey. Before they could 
only create using POST and its key was never decoded.

> dev rest api should allow '.' and '/' characters in region keys
> ---------------------------------------------------------------
>
>                 Key: GEODE-7938
>                 URL: https://issues.apache.org/jira/browse/GEODE-7938
>             Project: Geode
>          Issue Type: Bug
>          Components: rest (dev)
>            Reporter: Darrel Schneider
>            Assignee: Darrel Schneider
>            Priority: Major
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> The dev rest api has multiple endpoints that can take region entry keys 
> either as path variables or as query parameters. If the key contains a "/" 
> then it can cause problems with parsing the URL. The '.' character also 
> causes problems.
> The operations and endpoints that do not allow '.' and '/' in region keys are:
> {noformat}
> GET, PUT, and DELETE on /v1/{region}/{keys}
> POST on /v1/{region}?key={key}
> {noformat}
> A solution should be found that does not break backwards compatibility but 
> that also allows these characters to be in the specified region key(s).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to