[
https://issues.apache.org/jira/browse/ASTERIXDB-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17319782#comment-17319782
]
ASF subversion and git services commented on ASTERIXDB-2872:
------------------------------------------------------------
Commit bcd71969e50bfbf36faa0c175c39266b55c602e0 in asterixdb's branch
refs/heads/master from Ian Maxon
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=bcd7196 ]
[ASTERIXDB-2872][API] UDF API changes for new DataverseName usage
- user model changes: yes
- storage format changes: no
- interface changes: yes
Details:
- Redo the API now that the canonical form of DataverseNames are
acceptable as an external interface.
- The path of the request encodes the library dataverse and name
- POST updates or creates libraries. "type" remains a field in the
multipart request rather than inferring based on the extension
as was done in the API before the previous patch
- DELETE again deletes libraries based on the same path they
were POSTed at.
- Minor dedupe on error printing in NcUdfApiServlet
Change-Id: Icec828b119fd959760281c4f4cc49449b179546b
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/10932
Integration-Tests: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Reviewed-by: Michael Blow <mb...@apache.org>
> Make UDF API more RESTful once more
> -----------------------------------
>
> Key: ASTERIXDB-2872
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2872
> Project: Apache AsterixDB
> Issue Type: Task
> Components: API - HTTP API
> Reporter: Ian Maxon
> Assignee: Ian Maxon
> Priority: Major
>
> The recent change of the UDF API was based on an implementation of
> DataverseNames that no longer really applies. Previously the canonical form
> was not considered suitable for outside consumption in APIs or elsewhere.
> Passing in multiple discrete parts was the proper way to dod things. Now that
> the canonical form separator is simply '/', the previous method of basically
> putting everything into POST and using multiple "dataverse" fields in the
> multipart request to maintain usability with multiparts is not necessary. The
> URL-encoded canonical name is intuitive enough.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
