[jira] [Commented] (ASTERIXDB-2182) Use JSON-like representation for parameters

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on ASTERIXDB-2182:
------------------------------------------------------------

Commit f3aa19fb150177e21e3cd35803672d38abdb0f6f in asterixdb's branch refs/heads/master from Till Westmann
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=f3aa19f ]

[ASTERIXDB-2182][SQL] Change merge policy syntax

- user model changes: yes
  - change the way a merge policy is specified
- storage format changes: no
- interface changes: no

details:
- previously, merge policies are specified as follows:
  <USING> <COMPACTION> <POLICY>
  prefix_merge (("number"="123"),("size"="456"));
- After this change, the policies are specified as:
  <WITH> {
    "merge-policy": {
      "name": "prefix",
      "parameters": { "number": 123, "size": 456 }
    }
  };

- compaction and policy are not key words anymore

Change-Id: I040f4c74cfa0170b8888128ad5f975e196658776
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2183
Sonar-Qube: Jenkins <je...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <je...@fulliautomatix.ics.uci.edu>
Contrib: Jenkins <je...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <je...@fulliautomatix.ics.uci.edu>
Reviewed-by: Till Westmann <ti...@apache.org>


> Use JSON-like representation for parameters
> -------------------------------------------
>
>                 Key: ASTERIXDB-2182
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2182
>             Project: Apache AsterixDB
>          Issue Type: Improvement
>          Components: AQL - Translator AQL, SQL - Translator SQL++
>            Reporter: Till
>
> Currently parameters to statements in SQL++ and AQL are provided using a custom syntax, e.g.
> {noformat}
> create dataset LineItem(LineItemType) primary key l_orderkey, l_linenumber 
> using compaction policy correlated-prefix
>     (("max-mergable-component-size"="1048576"),
>      ("max-tolerance-component-count"="3"));
> {noformat}
> Instead of using this custom syntax, we should use a JSON-like syntax that aligns better with our data model.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)