Change in asterixdb[master]: [ASTERIXDB-2579][DOC] Document uuid/upsert/insert behavior
Michael Carey has posted comments on this change. ( https://asterix-gerrit.ics.uci.edu/3414 ) Change subject: [ASTERIXDB-2579][DOC] Document uuid/upsert/insert behavior .. Patch Set 2: (6 comments) https://asterix-gerrit.ics.uci.edu/#/c/3414/2/asterixdb/asterix-doc/src/main/markdown/sqlpp/5_ddl_dml.md File asterixdb/asterix-doc/src/main/markdown/sqlpp/5_ddl_dml.md: https://asterix-gerrit.ics.uci.edu/#/c/3414/2/asterixdb/asterix-doc/src/main/markdown/sqlpp/5_ddl_dml.md@31 PS2, Line 31: it's it's --> it is (more formal for doc purposes :-)) https://asterix-gerrit.ics.uci.edu/#/c/3414/2/asterixdb/asterix-doc/src/main/markdown/sqlpp/5_ddl_dml.md@53 PS2, Line 53: however, but https://asterix-gerrit.ics.uci.edu/#/c/3414/2/asterixdb/asterix-doc/src/main/markdown/sqlpp/5_ddl_dml.md@53 PS2, Line 53: as as its https://asterix-gerrit.ics.uci.edu/#/c/3414/2/asterixdb/asterix-doc/src/main/markdown/sqlpp/5_ddl_dml.md@53 PS2, Line 53: key, this key. This https://asterix-gerrit.ics.uci.edu/#/c/3414/2/asterixdb/asterix-doc/src/main/markdown/sqlpp/5_ddl_dml.md@53 PS2, Line 53: with with an https://asterix-gerrit.ics.uci.edu/#/c/3414/2/asterixdb/asterix-doc/src/main/markdown/sqlpp/5_ddl_dml.md@54 PS2, Line 54: that's the operation will be -- To view, visit https://asterix-gerrit.ics.uci.edu/3414 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I7ba526c79de8cb744dc41ebc797389e68333c5ce Gerrit-Change-Number: 3414 Gerrit-PatchSet: 2 Gerrit-Owner: Hussain Towaileb Gerrit-Reviewer: Anon. E. Moose (1000171) Gerrit-Reviewer: Jenkins Gerrit-Reviewer: Michael Carey Gerrit-Reviewer: Till Westmann Gerrit-Comment-Date: Tue, 28 May 2019 21:21:26 + Gerrit-HasComments: Yes
Change in asterixdb[master]: [ASTERIXDB-2456][DOC] Re-add insert to primer
Michael Carey has submitted this change and it was merged. Change subject: [ASTERIXDB-2456][DOC] Re-add insert to primer .. [ASTERIXDB-2456][DOC] Re-add insert to primer Change-Id: I404246ea4a8568e28190cd2371356175db1471cc Reviewed-on: https://asterix-gerrit.ics.uci.edu/2983 Sonar-Qube: Jenkins Tested-by: Jenkins Contrib: Jenkins Integration-Tests: Jenkins Reviewed-by: Michael Carey --- M asterixdb/asterix-doc/src/site/markdown/sqlpp/primer-sqlpp.md 1 file changed, 30 insertions(+), 0 deletions(-) Approvals: Anon. E. Moose #1000171: Michael Carey: Looks good to me, approved Jenkins: Verified; No violations found; ; Verified diff --git a/asterixdb/asterix-doc/src/site/markdown/sqlpp/primer-sqlpp.md b/asterixdb/asterix-doc/src/site/markdown/sqlpp/primer-sqlpp.md index 1c78cc4..40b81d6 100644 --- a/asterixdb/asterix-doc/src/site/markdown/sqlpp/primer-sqlpp.md +++ b/asterixdb/asterix-doc/src/site/markdown/sqlpp/primer-sqlpp.md @@ -850,6 +850,36 @@ { "chirp": { "chirpId": "5", "user": { "screenName": "NathanGiesen@211", "lang": "en", "friendsCount": 39339, "statusesCount": 473, "name": "Nathan Giesen", "followersCount": 49416 }, "senderLocation": point("40.09,92.69"), "sendTime": datetime("2006-08-04T10:10:00.000Z"), "referredTopics": {{ "product-w", "speed" }}, "messageText": " can't stand product-w its speed is terrible:(" }, "similarChirps": [ ] } { "chirp": { "chirpId": "8", "user": { "screenName": "NathanGiesen@211", "lang": "en", "friendsCount": 39339, "statusesCount": 473, "name": "Nathan Giesen", "followersCount": 49416 }, "senderLocation": point("46.05,93.34"), "sendTime": datetime("2005-10-14T10:10:00.000Z"), "referredTopics": {{ "product-z", "shortcut-menu" }}, "messageText": " like product-z the shortcut-menu is awesome:)" }, "similarChirps": [ ] } +## Inserting New Data ### +In addition to loading and querying data, AsterixDB supports incremental additions to datasets via the SQL++ _INSERT_ statement. + +The following example adds a new chirp by user "NathanGiesen@211" to the ChirpMessages dataset. +(An astute reader may notice that this chirp was issued a half an hour after his last chirp, so his counts +have all gone up in the interim, although he appears not to have moved in the last half hour.) + +USE TinySocial; + +INSERT INTO ChirpMessages +( + {"chirpId": "13", +"user": +{"screenName": "NathanGiesen@211", + "lang": "en", + "friendsCount": 39345, + "statusesCount": 479, + "name": "Nathan Giesen", + "followersCount": 49420 +}, +"senderLocation": point("47.44,80.65"), +"sendTime": datetime("2008-04-26T10:10:35"), +"referredTopics": {{"chirping"}}, +"messageText": "chirpy chirp, my fellow chirpers!" + } +); + +In general, the data to be inserted may be specified using any valid SQL++ query expression. +The insertion of a single object instance, as in this example, is just a special case where +the query expression happens to be a object constructor involving only constants. ### Deleting Existing Data ### In addition to inserting new data, AsterixDB supports deletion from datasets via the SQL++ _DELETE_ statement. -- To view, visit https://asterix-gerrit.ics.uci.edu/2983 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: merged Gerrit-Change-Id: I404246ea4a8568e28190cd2371356175db1471cc Gerrit-PatchSet: 2 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Ian Maxon Gerrit-Reviewer: Anon. E. Moose #1000171 Gerrit-Reviewer: Jenkins Gerrit-Reviewer: Michael Carey
Change in asterixdb[master]: [ASTERIXDB-2456][DOC] Re-add insert to primer
Michael Carey has posted comments on this change. Change subject: [ASTERIXDB-2456][DOC] Re-add insert to primer .. Patch Set 1: Code-Review+2 -- To view, visit https://asterix-gerrit.ics.uci.edu/2983 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: comment Gerrit-Change-Id: I404246ea4a8568e28190cd2371356175db1471cc Gerrit-PatchSet: 1 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Ian Maxon Gerrit-Reviewer: Anon. E. Moose #1000171 Gerrit-Reviewer: Jenkins Gerrit-Reviewer: Michael Carey Gerrit-HasComments: No
Change in asterixdb[master]: Document the Query Service API
Michael Carey has submitted this change and it was merged. Change subject: Document the Query Service API .. Document the Query Service API Change-Id: Ifcefb1671ea305a5958c9a74a588b4aaa17f399f Reviewed-on: https://asterix-gerrit.ics.uci.edu/1698 Sonar-Qube: JenkinsTested-by: Jenkins BAD: Jenkins Integration-Tests: Jenkins Reviewed-by: Till Westmann Reviewed-by: Michael Carey --- M asterixdb/asterix-doc/src/site/markdown/api.md 1 file changed, 157 insertions(+), 286 deletions(-) Approvals: Michael Carey: Looks good to me, approved Till Westmann: Looks good to me, approved Jenkins: Verified; No violations found; No violations found; Verified diff --git a/asterixdb/asterix-doc/src/site/markdown/api.md b/asterixdb/asterix-doc/src/site/markdown/api.md index 2e2f08c..848f2c3 100644 --- a/asterixdb/asterix-doc/src/site/markdown/api.md +++ b/asterixdb/asterix-doc/src/site/markdown/api.md @@ -21,324 +21,195 @@ ## Table of Contents -* [DDL API](#DdlApi) -* [Update API](#UpdateApi) -* [Query API](#QueryApi) -* [Mixed API](#AnyApi) -* [Asynchronous Result API](#AsynchronousResultApi) -* [Query Status API](#QueryStatusApi) -* [Error Codes](#ErrorCodes) +* [Query Service API](#queryservice) +* [Query Status API](#querystatus) +* [Query Result API](#queryresult) +## POST /query/service [Back to TOC] -## DDL API [Back to TOC] ## +__Description__ Returns result for query as JSON. + The response is a JSON object that contains some result metadata along with either an embedded result or an opaque + handle that can be used to navigate to the result (see the decription of the `mode` parameter for more details). -*End point for the data definition statements* +__Parameters__ -Endpoint: _/ddl_ +* `statement` - Specifies at least one valid SQL++ statement to run. The statements need to be urlencoded. Required. +* `pretty` - If the parameter `pretty` is given with the value `true`, the result will be indented. (Optional) +* `client_context_id` - A user-defined sequence of characters that the API receives and returns unchanged. This can be + used e.g. to match individual requests, jobs, and responses. Another option could be to use it for groups of requests + if an application decides to put e.g. an group identifier into that field to route groups of responses to a + particular response processor. +* `mode` - Result delivery mode. Possible values are `immediate`, `deferred`, `async` (default: `immediate`). + If the delivery mode is `immediate` the query result is returned with the response. + If the delivery mode is `deferred` the response contains a handle to the result. + If the delivery mode is `async` the response contains a handle to the query's status. -Parameters: +__Command (immediate result delivery)__ - - - Parameter - Description - Required? - - - ddl - String containing DDL statements to modify Metadata - Yes - - +$ curl -v --data-urlencode "statement=select 1;" \ + --data pretty=true \ + --data client_context_id=xyz \ + http://localhost:19002/query/service -This call does not return any result. If the operations were successful, HTTP OK status code is returned. +__Sample response__ -### Example ### - - DDL Statements - - -drop dataverse company if exists; -create dataverse company; -use dataverse company; - -create type Emp as open { - id : int32, - name : string -}; - -create dataset Employee(Emp) primary key id; - - -API call for the above DDL statements in the URL-encoded form. - -[http://localhost:19002/ddl?ddl=drop%20dataverse%20company%20if%20exists;create%20dataverse%20company;use%20dataverse%20company;create%20type%20Emp%20as%20open%20{id%20:%20int32,name%20:%20string};create%20dataset%20Employee(Emp)%20primary%20key%20id;](http://localhost:19002/ddl?ddl=drop%20dataverse%20company%20if%20exists;create%20dataverse%20company;use%20dataverse%20company;create%20type%20Emp%20as%20open%20{id%20:%20int32,name%20:%20string};create%20dataset%20Employee(Emp)%20primary%20key%20id;) - - Response -*HTTP OK 200* -`` - -## Update API [Back to TOC] ## - -*End point for update statements (INSERT, DELETE and LOAD)* - -Endpoint: _/update_ - -Parameters: - - - - Parameter - Description - Required? - - - statements - String containing update (insert/delete) statements to execute - Yes - - - -This call does not return any result. If the operations were successful, HTTP OK status code is returned. - -### Example ### - - Update Statements - - -use dataverse company; - -insert into dataset Employee({
Change in asterixdb[master]: Document the Query Service API
Michael Carey has posted comments on this change. Change subject: Document the Query Service API .. Patch Set 5: Code-Review+2 Correcting a sign bit error. :-) -- To view, visit https://asterix-gerrit.ics.uci.edu/1698 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: comment Gerrit-Change-Id: Ifcefb1671ea305a5958c9a74a588b4aaa17f399f Gerrit-PatchSet: 5 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Till WestmannGerrit-Reviewer: Jenkins Gerrit-Reviewer: Jianfeng Jia Gerrit-Reviewer: Michael Carey Gerrit-Reviewer: Till Westmann Gerrit-Reviewer: Xikui Wang Gerrit-HasComments: No
Change in asterixdb[master]: Document the Query Service API
Michael Carey has posted comments on this change. Change subject: Document the Query Service API .. Patch Set 4: Code-Review-2 (1 comment) (Found one last tiny typo, but it looks good!) https://asterix-gerrit.ics.uci.edu/#/c/1698/4/asterixdb/asterix-doc/src/site/markdown/api.md File asterixdb/asterix-doc/src/site/markdown/api.md: PS4, Line 189: plain is plain result --> is a plain result -- To view, visit https://asterix-gerrit.ics.uci.edu/1698 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: comment Gerrit-Change-Id: Ifcefb1671ea305a5958c9a74a588b4aaa17f399f Gerrit-PatchSet: 4 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Till WestmannGerrit-Reviewer: Jenkins Gerrit-Reviewer: Jianfeng Jia Gerrit-Reviewer: Michael Carey Gerrit-Reviewer: Till Westmann Gerrit-Reviewer: Xikui Wang Gerrit-HasComments: Yes
Change in asterixdb[master]: Document the Query Service API
Michael Carey has posted comments on this change. Change subject: Document the Query Service API .. Patch Set 1: (4 comments) I've added a few comments... https://asterix-gerrit.ics.uci.edu/#/c/1698/1/asterixdb/asterix-doc/src/site/markdown/api.md File asterixdb/asterix-doc/src/site/markdown/api.md: Line 43: __Command (immedidate result delivery)__ immedidate -> immediate Line 45: $ curl -v --data-urlencode "statement=select 1;" \ I would suggest using a slightly more interesting query here - partly to make the results a little more illustrative on the JSON side, partly to clarify some encoding questions that might arise, and partly to make the timings a bit more illustrative on the performance side in the async case (maybe). E.g.: SELECT ds.BucketName, ds.DatasetName, ds.`Filter` FROM Metadata.`Dataset` ds WHERE ds.DataverseName LIKE "D%"; Line 157: $ curl -v http://localhost:19002/query/service/status/9-0 What is the /9-0 suffix here? More generally, maybe there needs to be a sentence about how one correlates the subsequent requests to the query request? I assume this is (somehow) the answer to that. :-) Line 182: $ curl -v http://localhost:19002/query/service/result/7-0 Same question/comment here. -- To view, visit https://asterix-gerrit.ics.uci.edu/1698 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: comment Gerrit-Change-Id: Ifcefb1671ea305a5958c9a74a588b4aaa17f399f Gerrit-PatchSet: 1 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Till WestmannGerrit-Reviewer: Jenkins Gerrit-Reviewer: Michael Carey Gerrit-HasComments: Yes
Change in asterixdb[master]: Added some info about open and close types to the data model...
Michael Carey has uploaded a new change for review. https://asterix-gerrit.ics.uci.edu/1510 Change subject: Added some info about open and close types to the data model doc. Change-Id: I1262090a2a568d935fd96e00db1da5cd836f25a5 .. Added some info about open and close types to the data model doc. Change-Id: I1262090a2a568d935fd96e00db1da5cd836f25a5 --- M asterixdb/asterix-doc/src/site/markdown/datamodel.md 1 file changed, 13 insertions(+), 4 deletions(-) git pull ssh://asterix-gerrit.ics.uci.edu:29418/asterixdb refs/changes/10/1510/1 diff --git a/asterixdb/asterix-doc/src/site/markdown/datamodel.md b/asterixdb/asterix-doc/src/site/markdown/datamodel.md index cba0d18..2c8a015 100644 --- a/asterixdb/asterix-doc/src/site/markdown/datamodel.md +++ b/asterixdb/asterix-doc/src/site/markdown/datamodel.md @@ -350,7 +350,7 @@ ### Missing ### -`missing` represents a missing name-value pair in a object. +`missing` represents a missing name-value pair in an object. If the referenced field does not exist, an empty result value is returned by the query. As neither the data model nor the system enforces homogeneity for datasets or collections, @@ -371,13 +371,22 @@ ## Derived Types ## ### Object### -A `object` contains a set of fields, where each field is described by its name and type. A object type is either open or closed. Open objects can contain fields that are not part of the type definition, while closed objects cannot. Syntactically, object constructors are surrounded by curly braces "{...}". +An `object` contains a set of fields, where each field is described by its name and type. An object type may be defined as either open or closed. Open objects (instances of open object types) are permitted to contain fields that are not part of the type definition, while closed objects do not permit their instances to carry extra fields. An example type definition for an object is: -An example would be +create type SoldierType as open { +name: string?, +rank: string, +serialno: int +}; +Syntactically, object constructors are surrounded by curly braces "{...}". +Some examples of legitimate instances of the above type include: -{ "id": 213508, "name": "Alice Bob" } +{ "name": "Joe Blow", "rank": "Sergeant", "serialno": 1234567 } +{ "rank": "Private", "serialno": 9876543 } +{ "name": "Sally Forth", "rank": "Major", "serialno": 2345678, "gender": "F" } +The first instance has all of the type's prescribed content. The second instance is missing the name field, which is fine because it is optional (due to the ?). The third instance has an extra field; that is fine because the type definition specifies that it is open (which is also true by default, if open is not specified). To more tightly control object content, specifying closed instead of open in the type definition for SoldierType would have made the third example instance an invalid instance of the type. ### Array### An `array` is a container that holds a fixed number of values. Array constructors are denoted by brackets: "[...]". -- To view, visit https://asterix-gerrit.ics.uci.edu/1510 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: newchange Gerrit-Change-Id: I1262090a2a568d935fd96e00db1da5cd836f25a5 Gerrit-PatchSet: 1 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Michael Carey
Change in asterixdb[master]: ASTERIXDB-1747 Implemented full lifecycle capabilities for d...
Michael Carey has posted comments on this change. Change subject: ASTERIXDB-1747 Implemented full lifecycle capabilities for distributed jobs .. Patch Set 11: Actually, regarding "Addressed comments. As far as tests go, the functionality is tested in BAD, which is run against all changes to Asterix, which should prevent regression." Nope! We need to make sure that we have tests along with code where the code lives - so the two options here would be to move the relevant unit tests up into master to make sure this is tested, or to move the code down into BAD where it is currently being tested. Either is fine. We can't have master depending on extensions for QA. Thx! -- To view, visit https://asterix-gerrit.ics.uci.edu/1377 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: comment Gerrit-Change-Id: I59c3422d5c1ab7756a6a4685ac527dfe50434954 Gerrit-PatchSet: 11 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Steven JacobsGerrit-Reviewer: Ian Maxon Gerrit-Reviewer: Jenkins Gerrit-Reviewer: Michael Carey Gerrit-Reviewer: Steven Jacobs Gerrit-Reviewer: Till Westmann Gerrit-Reviewer: Xikui Wang Gerrit-Reviewer: Yingyi Bu Gerrit-Reviewer: abdullah alamoudi Gerrit-HasComments: No
Change in incubator-asterixdb-site[asf-site]: Remove javascript SDK doc
Michael Carey has posted comments on this change. Change subject: Remove javascript SDK doc .. Patch Set 1: Code-Review+2 Looks great! -- To view, visit https://asterix-gerrit.ics.uci.edu/1455 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: comment Gerrit-Change-Id: Ic73d43db6a1dc76a4c454c983ada1fd9226f67ef Gerrit-PatchSet: 1 Gerrit-Project: incubator-asterixdb-site Gerrit-Branch: asf-site Gerrit-Owner: Ian MaxonGerrit-Reviewer: Jenkins Gerrit-Reviewer: Michael Carey Gerrit-Reviewer: Till Westmann Gerrit-HasComments: No
Change in asterixdb[master]: Fixing some doc bugs related to numeric functions.
Hello Jenkins, I'd like you to reexamine a change. Please visit https://asterix-gerrit.ics.uci.edu/1312 to look at the new patch set (#3). Change subject: Fixing some doc bugs related to numeric functions. .. Fixing some doc bugs related to numeric functions. Change-Id: I692586bb408f4d939b4d16bdaf784822c60c9aca --- M asterixdb/asterix-doc/src/main/markdown/builtins/1_numeric.md 1 file changed, 10 insertions(+), 10 deletions(-) git pull ssh://asterix-gerrit.ics.uci.edu:29418/asterixdb refs/changes/12/1312/3 -- To view, visit https://asterix-gerrit.ics.uci.edu/1312 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: newpatchset Gerrit-Change-Id: I692586bb408f4d939b4d16bdaf784822c60c9aca Gerrit-PatchSet: 3 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Michael CareyGerrit-Reviewer: Jenkins Gerrit-Reviewer: Yingyi Bu
Change in asterixdb[master]: Fixing some doc bugs related to numeric functions.
Michael Carey has uploaded a new change for review. https://asterix-gerrit.ics.uci.edu/1312 Change subject: Fixing some doc bugs related to numeric functions. .. Fixing some doc bugs related to numeric functions. Change-Id: I692586bb408f4d939b4d16bdaf784822c60c9aca --- M asterixdb/asterix-doc/src/main/markdown/builtins/1_numeric.md 1 file changed, 10 insertions(+), 10 deletions(-) git pull ssh://asterix-gerrit.ics.uci.edu:29418/asterixdb refs/changes/12/1312/1 diff --git a/asterixdb/asterix-doc/src/main/markdown/builtins/1_numeric.md b/asterixdb/asterix-doc/src/main/markdown/builtins/1_numeric.md index 7cdc63f..39f8689 100644 --- a/asterixdb/asterix-doc/src/main/markdown/builtins/1_numeric.md +++ b/asterixdb/asterix-doc/src/main/markdown/builtins/1_numeric.md @@ -60,12 +60,12 @@ * Example: -{ "v1": acos(1), "v2": acos(2), "v3": abs(0), "v4": acos(float("0.5")), "v5": acos(double("-0.5")) }; +{ "v1": acos(1), "v2": acos(2), "v3": acos(0), "v4": acos(float("0.5")), "v5": acos(double("-0.5")) }; * The expected result is: -{ "v1": 0.0, "v2": NaN, "v3": 0, "v4": 1.0471975511965979, "v5": 2.0943951023931957 } +{ "v1": 0.0, "v2": "NaN", "v3": 1.5707963267948966, "v4": 1.0471975511965979, "v5": 2.0943951023931957 } ### asin ### @@ -123,7 +123,7 @@ atan2(numeric_value1, numeric_value2) - * Computes the arc tangent value of arguments. + * Computes the arc tangent value of numeric_value2/numeric_value1. * Arguments: * `numeric_value1`: a `tinyint`/`smallint`/`integer`/`bigint`/`float`/`double` value, * `numeric_value2`: a `tinyint`/`smallint`/`integer`/`bigint`/`float`/`double` value. @@ -268,12 +268,12 @@ * Example: -{ "v1": exp(1), "v2": exp(2), "v3": exp(0), "v4": exp(float("0.5")), "v5": exp(double("1000")) }; +{ "v1": ln(1), "v2": ln(2), "v3": ln(0), "v4": ln(float("0.5")), "v5": ln(double("1000")) }; * The expected result is: -{ "v1": 2.718281828459045, "v2": 7.38905609893065, "v3": 1.0, "v4": 1.6487212707001282, "v5": Infinity } +{ "v1": 0.0, "v2": 0.6931471805599453, "v3": "-Infinity", "v4": -0.6931471805599453, "v5": 6.907755278982137 } ### log ### @@ -292,15 +292,15 @@ * Example: -{ "v1": exp(1), "v2": exp(2), "v3": exp(0), "v4": exp(float("0.5")), "v5": exp(double("1000")) }; - +{ "v1": log(1), "v2": log(2), "v3": log(0), "v4": log(float("0.5")), "v5": log(double("1000")) }; * The expected result is: -{ "v1": 2.718281828459045, "v2": 7.38905609893065, "v3": 1.0, "v4": 1.6487212707001282, "v5": Infinity } +{ "v1": 0.0, "v2": 0.3010299956639812, "v3": "-Infinity", "v4": -0.3010299956639812, "v5": 3.0 } -### atan2 ### + +### power ### * Syntax: power(numeric_value1, numeric_value2) @@ -409,7 +409,7 @@ * Example: -{ "v1": sign(1), "v2": sign(2), "v3": sign(0), "v4": sign(float("0.5")), "v5": sign(double("1000")) }; +{ "v1": sign(1), "v2": sign(2), "v3": sign(0), "v4": sign(float("0.5")), "v5": sign(double("-1000")) }; * The expected result is: -- To view, visit https://asterix-gerrit.ics.uci.edu/1312 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: newchange Gerrit-Change-Id: I692586bb408f4d939b4d16bdaf784822c60c9aca Gerrit-PatchSet: 1 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Michael Carey
Change in asterixdb[master]: Making the SQL++ reference manual a bit more generic in how ...
Michael Carey has uploaded a new change for review. https://asterix-gerrit.ics.uci.edu/1237 Change subject: Making the SQL++ reference manual a bit more generic in how it reads. .. Making the SQL++ reference manual a bit more generic in how it reads. Change-Id: I184ede1398de3190b60bec2947d826bdc5278594 --- M asterixdb/asterix-doc/src/main/markdown/sqlpp/1_intro.md M asterixdb/asterix-doc/src/main/markdown/sqlpp/2_expr.md M asterixdb/asterix-doc/src/main/markdown/sqlpp/3_query.md M asterixdb/asterix-doc/src/main/markdown/sqlpp/4_ddl.md 4 files changed, 46 insertions(+), 31 deletions(-) git pull ssh://asterix-gerrit.ics.uci.edu:29418/asterixdb refs/changes/37/1237/1 diff --git a/asterixdb/asterix-doc/src/main/markdown/sqlpp/1_intro.md b/asterixdb/asterix-doc/src/main/markdown/sqlpp/1_intro.md index ed8d1c9..442de41 100644 --- a/asterixdb/asterix-doc/src/main/markdown/sqlpp/1_intro.md +++ b/asterixdb/asterix-doc/src/main/markdown/sqlpp/1_intro.md @@ -1,6 +1,21 @@ # 1. Introduction -This document is intended as a reference guide to the full syntax and semantics of the SQL++ Query Language, a SQL-inspired language for working with semistructured data. SQL++ has much in common with SQL, but there are also differences due to the data model that the language is designed to serve. (SQL was designed in the 1970's for interacting with the flat, schema-ified world of relational databases, while SQL++ is designed for the nested, schema-less/schema-optional world of modern NoSQL systems.) In particular, SQL++ in the context of Apache AsterixDB is intended for working with the Asterix Data Model (ADM), which is a data model aimed at a superset of JSON with an enriched and flexible type system. +This document is intended as a reference guide to the full syntax and semantics of +the SQL++ Query Language, a SQL-inspired language for working with semistructured data. +SQL++ has much in common with SQL, but some differences do exist due to the different +data models that the two languages were designed to serve. +SQL was designed in the 1970's for interacting with the flat, schema-ified world of +relational databases, while SQL++ is much newer and targets the nested, schema-optional +(or even schema-less) world of modern NoSQL systems. -New AsterixDB users are encouraged to read and work through the (friendlier) guide "AsterixDB 101: An ADM and SQL++ Primer" before attempting to make use of this document. In addition, readers are advised to read and understand the Asterix Data Model (ADM) reference guide since a basic understanding of ADM concepts is a prerequisite to understanding SQL++. In what follows, we detail the features of the SQL++ language in a grammar-guided manner: we list and briefly explain each of the productions in the SQL++ grammar, offering examples (and results) for clarity. +In the context of Apache AsterixDB, SQL++ is intended for working with the Asterix Data Model (ADM), +a data model based on a superset of JSON with an enriched and flexible type system. +New AsterixDB users are encouraged to read and work through the (much friendlier) guide +"AsterixDB 101: An ADM and SQL++ Primer" before attempting to make use of this document. +In addition, readers are advised to read through the Asterix Data Model (ADM) reference guide +first as well, as an understanding of the data model is a prerequisite to understanding SQL++. + +In what follows, we detail the features of the SQL++ language in a grammar-guided manner. +We list and briefly explain each of the productions in the SQL++ grammar, offering examples +(and results) for clarity. diff --git a/asterixdb/asterix-doc/src/main/markdown/sqlpp/2_expr.md b/asterixdb/asterix-doc/src/main/markdown/sqlpp/2_expr.md index 79f9da0..b4ac619 100644 --- a/asterixdb/asterix-doc/src/main/markdown/sqlpp/2_expr.md +++ b/asterixdb/asterix-doc/src/main/markdown/sqlpp/2_expr.md @@ -2,7 +2,7 @@ Expression ::= OperatorExpression | CaseExpression | QuantifiedExpression -SQL++ is a highly composable expression language. Each SQL++ expression returns zero or more Asterix Data Model (ADM) instances. There are three major kinds of expressions in SQL++. At the topmost level, a SQL++ expression can be an OperatorExpression (similar to a mathematical expression), an ConditionalExpression (to choose between alternative values), or a QuantifiedExpression (which yields a boolean value). Each will be detailed as we explore the full SQL++ grammar. +SQL++ is a highly composable expression language. Each SQL++ expression returns zero or more data model instances. There are three major kinds of expressions in SQL++. At the topmost level, a SQL++ expression can be an OperatorExpression (similar to a mathematical expression), an ConditionalExpression (to choose between alternative values), or a QuantifiedExpression (which yields a boolean value). Each will be
Change in asterixdb[master]: Minor edits to LET, UNION ALL, and SQL++ vs. SQL table.
Hello Jenkins, I'd like you to reexamine a change. Please visit https://asterix-gerrit.ics.uci.edu/1200 to look at the new patch set (#2). Change subject: Minor edits to LET, UNION ALL, and SQL++ vs. SQL table. .. Minor edits to LET, UNION ALL, and SQL++ vs. SQL table. Change-Id: I3cd80a67dca523fb6f34089ef5073fd6bef39e1e --- M asterixdb/asterix-doc/src/main/markdown/sqlpp/3_query.md 1 file changed, 15 insertions(+), 15 deletions(-) git pull ssh://asterix-gerrit.ics.uci.edu:29418/asterixdb refs/changes/00/1200/2 -- To view, visit https://asterix-gerrit.ics.uci.edu/1200 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: newpatchset Gerrit-Change-Id: I3cd80a67dca523fb6f34089ef5073fd6bef39e1e Gerrit-PatchSet: 2 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Michael CareyGerrit-Reviewer: Jenkins Gerrit-Reviewer: Yingyi Bu
Change in asterixdb[master]: Minor updates to the reference material for SQL++.
Michael Carey has abandoned this change. Change subject: Minor updates to the reference material for SQL++. .. Abandoned Oops. Sorry. Shouldn't have submitted this change this way! -- To view, visit https://asterix-gerrit.ics.uci.edu/1131 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: abandon Gerrit-Change-Id: I299b4947b928f301e8fdca8522d9a9f1e6a772cb Gerrit-PatchSet: 4 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Michael CareyGerrit-Reviewer: Ian Maxon Gerrit-Reviewer: Jenkins Gerrit-Reviewer: Jianfeng Jia Gerrit-Reviewer: Taewoo Kim Gerrit-Reviewer: Till Westmann Gerrit-Reviewer: Yingyi Bu
Change in asterixdb[master]: Separate submit of minor edits to LET, UNION ALL, and SQL++ ...
Michael Carey has uploaded a new change for review. https://asterix-gerrit.ics.uci.edu/1200 Change subject: Separate submit of minor edits to LET, UNION ALL, and SQL++ vs. SQL table. .. Separate submit of minor edits to LET, UNION ALL, and SQL++ vs. SQL table. commit 07dd012eee2a057883b9e9e2da164b7cd118911f Author: Mike CareyDate: Thu Sep 22 17:52:19 2016 -0700 Minor edits to LET, UNION ALL, and SQL++ vs. SQL table. Change-Id: I3cd80a67dca523fb6f34089ef5073fd6bef39e1e --- M asterixdb/asterix-doc/src/main/markdown/sqlpp/3_query.md 1 file changed, 15 insertions(+), 15 deletions(-) git pull ssh://asterix-gerrit.ics.uci.edu:29418/asterixdb refs/changes/00/1200/1 diff --git a/asterixdb/asterix-doc/src/main/markdown/sqlpp/3_query.md b/asterixdb/asterix-doc/src/main/markdown/sqlpp/3_query.md index 01aa358..04d8e5b 100644 --- a/asterixdb/asterix-doc/src/main/markdown/sqlpp/3_query.md +++ b/asterixdb/asterix-doc/src/main/markdown/sqlpp/3_query.md @@ -779,15 +779,15 @@ element, to "de-listify" the list and obtain the desired scalar for the comparison. ## LET clauses -Similar to `WITH` clauses, `LET` clauses can be useful when a (complex) expression is used several times in a query, such that the query can be more concise. The next query shows an example. +Similar to `WITH` clauses, `LET` clauses can be useful when a (complex) expression is used several times within a query, allowing it to be written once to make the query more concise. The next query shows an example. # Example SELECT u.name AS uname, messages AS messages FROM GleambookUsers u -LET messages = ( SELECT VALUE m - FROM GleambookMessages m - WHERE m.authorId = u.id ) +LET messages = (SELECT VALUE m +FROM GleambookMessages m +WHERE m.authorId = u.id) WHERE EXISTS messages; This query lists `GleambookUsers` that have posted `GleambookMessages` and shows all authored messages for each listed user. It returns: @@ -807,17 +807,17 @@ WHERE EXISTS ( SELECT VALUE m FROM GleambookMessages m WHERE m.authorId = u.id -); + ); ## UNION ALL -UNION ALL can be used to combine two input streams into one. Similar to SQL, there is no ordering guarantee on the output stream. However, different from SQL, SQL++ does not inspect what the data looks like on each input stream and allows heterogenity on the output stream and does not enforce schema change on any input streams. The following query is an example: +UNION ALL can be used to combine two input streams into one. As in SQL, there is no ordering guarantee on the contents of the output stream. However, unlike SQL, SQL++ does not constrain what the data looks like on the input streams; in particular, it allows heterogenity on the input and output streams. The following odd but legal query is an example: # Example SELECT u.name AS uname FROM GleambookUsers u WHERE u.id = 2 -UNION ALL + UNION ALL SELECT VALUE m.message FROM GleambookMessages m WHERE authorId=2; @@ -864,18 +864,18 @@ | Feature | SQL++ | SQL-92 | |--||| -| SELECT * | Returns nested records. | Returns flattened concatenated records. | -| Subquery | Returns a collection. | The returned collection of records is cast into a scalar value if the subquery appears in a SELECT list or on one side of a comparison or as input to a function. | -| Left outer join | Fills in `MISSING` for non-matches. | Fills in `NULL`(s) for non-matches.| -| Union All | Allows heterogenous input and does not enforce schema changes on data. | Different input streams have to follow equivalent structural types and output field names for non-first input streams have to be be changed to be the same as that of the first input stream. -| String literal | Double quotes or single quotes. | Single quotes only. | -| Delimited identifiers | Backticks. | Double quotes. | +| SELECT * | Returns nested records | Returns flattened concatenated records | +| Subquery | Returns a collection | The returned collection is cast into a scalar value if the subquery appears in a SELECT list or on one side of a comparison or as input to a function | +| LEFT OUTER JOIN | Fills in `MISSING` for non-matches | Fills in `NULL`(s) for non-matches| +| UNION ALL | Allows heterogenous inputs and output | Input streams must be UNION-compatible and output field names are drawn from the first input stream +| String literal | Double quotes or single quotes | Single quotes only | +| Delimited identifiers | Backticks | Double quotes | -For things beyond the cheat sheet, SQL++ is SQL-92 compliant. +For things beyond this cheat sheet, SQL++ is SQL-92 compliant. Morever, SQL++ offers the following additional
Change in asterixdb[master]: Updating the new 101 tutorial's link for SQL++.
Hello Jenkins, I'd like you to reexamine a change. Please visit https://asterix-gerrit.ics.uci.edu/1131 to look at the new patch set (#3). Change subject: Updating the new 101 tutorial's link for SQL++. .. Updating the new 101 tutorial's link for SQL++. Includes SQL++ versions of all 101 queries (sometimes > one). Also includes new/updated example data. Now includes addressing of round one comments. Also updated in anticipation of a couple of Yingyi's changes. Fixed the sidebar access as well now. Change-Id: I299b4947b928f301e8fdca8522d9a9f1e6a772cb --- A asterixdb/asterix-doc/src/site/markdown/sqlpp/primer-sqlpp.md A asterixdb/asterix-doc/src/site/resources/data/chm.adm A asterixdb/asterix-doc/src/site/resources/data/chu.adm A asterixdb/asterix-doc/src/site/resources/data/gbm.adm A asterixdb/asterix-doc/src/site/resources/data/gbu.adm M asterixdb/asterix-doc/src/site/site.xml 6 files changed, 967 insertions(+), 0 deletions(-) git pull ssh://asterix-gerrit.ics.uci.edu:29418/asterixdb refs/changes/31/1131/3 -- To view, visit https://asterix-gerrit.ics.uci.edu/1131 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: newpatchset Gerrit-Change-Id: I299b4947b928f301e8fdca8522d9a9f1e6a772cb Gerrit-PatchSet: 3 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Michael CareyGerrit-Reviewer: Ian Maxon Gerrit-Reviewer: Jenkins Gerrit-Reviewer: Jianfeng Jia Gerrit-Reviewer: Taewoo Kim Gerrit-Reviewer: Till Westmann Gerrit-Reviewer: Yingyi Bu
Change in asterixdb[master]: Updating the new 101 tutorial for SQL++.
Hello Jenkins, I'd like you to reexamine a change. Please visit https://asterix-gerrit.ics.uci.edu/1131 to look at the new patch set (#2). Change subject: Updating the new 101 tutorial for SQL++. .. Updating the new 101 tutorial for SQL++. Includes SQL++ versions of all 101 queries (sometimes > one). Also includes new/updated example data. Now includes addressing of round one comments. Also updated in anticipation of a couple of Yingyi's changes. Change-Id: I299b4947b928f301e8fdca8522d9a9f1e6a772cb --- A asterixdb/asterix-doc/src/site/markdown/sqlpp/primer-sqlpp.md A asterixdb/asterix-doc/src/site/resources/data/chm.adm A asterixdb/asterix-doc/src/site/resources/data/chu.adm A asterixdb/asterix-doc/src/site/resources/data/gbm.adm A asterixdb/asterix-doc/src/site/resources/data/gbu.adm M asterixdb/asterix-doc/src/site/site.xml 6 files changed, 967 insertions(+), 0 deletions(-) git pull ssh://asterix-gerrit.ics.uci.edu:29418/asterixdb refs/changes/31/1131/2 -- To view, visit https://asterix-gerrit.ics.uci.edu/1131 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: newpatchset Gerrit-Change-Id: I299b4947b928f301e8fdca8522d9a9f1e6a772cb Gerrit-PatchSet: 2 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Michael CareyGerrit-Reviewer: Ian Maxon Gerrit-Reviewer: Jenkins Gerrit-Reviewer: Jianfeng Jia Gerrit-Reviewer: Taewoo Kim Gerrit-Reviewer: Till Westmann Gerrit-Reviewer: Yingyi Bu
Change in asterixdb[master]: Enhanced Insert AQL
Michael Carey has posted comments on this change. Change subject: Enhanced Insert AQL .. Patch Set 10: I couldn't figure out how to publish my comment on Till's comment - but the gist is I like the variant: insert into dataset b as $b ( for $a in dataset a where $a.x > 5 return $a ) returning func($b) Where func($b) is a placeholder for any AQL query involving $b. -- To view, visit https://asterix-gerrit.ics.uci.edu/1150 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: comment Gerrit-Change-Id: I65789d2a861d15232dd29156a6987d0635ec6c94 Gerrit-PatchSet: 10 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Steven JacobsGerrit-Reviewer: Jenkins Gerrit-Reviewer: Michael Carey Gerrit-Reviewer: Steven Jacobs Gerrit-Reviewer: Till Westmann Gerrit-Reviewer: Yingyi Bu Gerrit-Reviewer: abdullah alamoudi Gerrit-HasComments: No
Change in asterixdb[master]: Enhanced Insert AQL
Michael Carey has posted comments on this change. Change subject: Enhanced Insert AQL .. Patch Set 10: I added a comment on the syntax - I would like to second Till's change (modulo finalizing the var-binding syntax). -- To view, visit https://asterix-gerrit.ics.uci.edu/1150 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: comment Gerrit-Change-Id: I65789d2a861d15232dd29156a6987d0635ec6c94 Gerrit-PatchSet: 10 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Steven JacobsGerrit-Reviewer: Jenkins Gerrit-Reviewer: Michael Carey Gerrit-Reviewer: Steven Jacobs Gerrit-Reviewer: Till Westmann Gerrit-Reviewer: Yingyi Bu Gerrit-Reviewer: abdullah alamoudi Gerrit-HasComments: No
Change in asterixdb[master]: Enhanced Insert AQL
Michael Carey has posted comments on this change. Change subject: Enhanced Insert AQL .. Patch Set 10: Code-Review-1 I added a common on the syntax - I would like to second Till's change (modulo finalizing the var-binding syntax). -- To view, visit https://asterix-gerrit.ics.uci.edu/1150 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: comment Gerrit-Change-Id: I65789d2a861d15232dd29156a6987d0635ec6c94 Gerrit-PatchSet: 10 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Steven JacobsGerrit-Reviewer: Jenkins Gerrit-Reviewer: Michael Carey Gerrit-Reviewer: Steven Jacobs Gerrit-Reviewer: Till Westmann Gerrit-Reviewer: Yingyi Bu Gerrit-Reviewer: abdullah alamoudi Gerrit-HasComments: No
Change in asterixdb[master]: Adding a new 101 tutorial for SQL++.
Michael Carey has uploaded a new change for review. https://asterix-gerrit.ics.uci.edu/1131 Change subject: Adding a new 101 tutorial for SQL++. .. Adding a new 101 tutorial for SQL++. Includes SQL++ versions of all 101 queries (sometimes > one). Also includes new/updated example data. Change-Id: I299b4947b928f301e8fdca8522d9a9f1e6a772cb --- A asterixdb/asterix-doc/src/site/markdown/sqlpp/primer-sqlpp.md A asterixdb/asterix-doc/src/site/resources/data/chm.adm A asterixdb/asterix-doc/src/site/resources/data/chu.adm A asterixdb/asterix-doc/src/site/resources/data/gbm.adm A asterixdb/asterix-doc/src/site/resources/data/gbu.adm 5 files changed, 954 insertions(+), 0 deletions(-) git pull ssh://asterix-gerrit.ics.uci.edu:29418/asterixdb refs/changes/31/1131/1 diff --git a/asterixdb/asterix-doc/src/site/markdown/sqlpp/primer-sqlpp.md b/asterixdb/asterix-doc/src/site/markdown/sqlpp/primer-sqlpp.md new file mode 100644 index 000..62a5875 --- /dev/null +++ b/asterixdb/asterix-doc/src/site/markdown/sqlpp/primer-sqlpp.md @@ -0,0 +1,913 @@ + + +# AsterixDB 101: An ADM and SQL++ Primer # + +## Welcome to AsterixDB! ## +This document introduces the main features of AsterixDB's data model (ADM) and its new SQL-like query language (SQL++) by example. +The example is a simple scenario involving (synthetic) sample data modeled after data from the social domain. +This document describes a set of sample datasets, together with a set of illustrative queries, +to introduce you to the "AsterixDB user experience". +The complete set of steps required to create and load a handful of sample datasets, along with runnable queries +and the expected results for each query, are included. + +This document assumes that you are at least vaguely familiar with AsterixDB and why you might want to use it. +Most importantly, it assumes you already have a running instance of AsterixDB and that you know how to query +it using AsterixDB's basic web interface. +For more information on these topics, you should go through the steps in +[Installing Asterix Using Managix](../install.html) +before reading this document and make sure that you have a running AsterixDB instance ready to go. +To get your feet wet, you should probably start with a simple local installation of AsterixDB on your favorite +machine, accepting all of the default settings that Managix offers. +Later you can graduate to trying AsterixDB on a cluster, its real intended home (since it targets Big Data). +(Note: With the exception of specifying the correct locations where you put the source data for this example, +there should no changes needed in the SQL++ statements to run the examples locally and/or to run them +on a cluster when you are ready to take that step.) + +As you read through this document, you should try each step for yourself on your own AsterixDB instance. +Once you have reached the end, you will be fully armed and dangerous, with all the basic AsterixDB knowledge +that you'll need to start down the path of modeling, storing, and querying your own semistructured data. + + +## ADM: Modeling Semistructed Data in AsterixDB ## +In this section you will learn all about modeling Big Data using +ADM, the data model of the AsterixDB BDMS. + +### Dataverses, Datatypes, and Datasets ### +The top-level organizing concept in the AsterixDB world is the _dataverse_. +A dataverse---short for "data universe"---is a place (similar to a database in a relational DBMS) in which +to create and manage the types, datasets, functions, and other artifacts for a given AsterixDB application. +When you start using an AsterixDB instance for the first time, it starts out "empty"; it contains no data +other than the AsterixDB system catalogs (which live in a special dataverse called the Metadata dataverse). +To store your data in AsterixDB, you will first create a dataverse and then you use it for the _datatypes_ +and _datasets_ for managing your own data. +A datatype tells AsterixDB what you know (or more accurately, what you want it to know) a priori about one +of the kinds of data instances that you want AsterixDB to hold for you. +A dataset is a collection of data instances of a datatype, +and AsterixDB makes sure that the data instances that you put in it conform to its specified type. +Since AsterixDB targets semistructured data, you can use _open_ datatypes and tell it as little or as +much as you wish about your data up front; the more you tell it up front, the less information it will +have to store repeatedly in the individual data instances that you give it. +Instances of open datatypes are permitted to have additional content, beyond what the datatype says, +as long as they at least contain the information prescribed by the datatype definition. +Open typing allows data to vary from one instance to another and it leaves wiggle room for application +evolution in terms of what
Change in asterixdb[master]: Fix open field CREATE INDEX syntax (AQL and SQLPP).
Michael Carey has submitted this change and it was merged. Change subject: Fix open field CREATE INDEX syntax (AQL and SQLPP). .. Fix open field CREATE INDEX syntax (AQL and SQLPP). Our CREATE INDEX syntax for open fields didn't match our semantics. Our semantics allow to-be-indexed open field(s) to be MISSING. We don't support (or offer :-)) tighter semantics than that. Our syntax didn't require creators to say this, but now it does: Old: CREATE INDEX myIdx on MyDSet(myTime: datetime) ENFORCED; New: CREATE INDEX myIdx on MyDSet(myTime: datetime?) ENFORCED; Have now addressed all of Till's comments (I think). Change-Id: I32bf8bc5ac1c0e6aa6744ca8f91a197311219814 Reviewed-on: https://asterix-gerrit.ics.uci.edu/1106 Reviewed-by: Yingyi BuSonar-Qube: Jenkins Tested-by: Jenkins Integration-Tests: Jenkins --- M asterixdb/asterix-app/src/test/resources/metadata/queries/basic/meta16/meta16.1.ddl.aql M asterixdb/asterix-app/src/test/resources/metadata/queries/basic/meta17/meta17.1.ddl.aql M asterixdb/asterix-app/src/test/resources/metadata/queries/basic/meta24/meta24.1.ddl.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/meta/secondary_index-lojoin_with_meta-1.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/meta/secondary_index-nljoin_with_meta-1.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/meta/secondary_index-nljoin_with_meta-2.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/meta/secondary_index_with_meta-2.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-index/rtree-index-join/spatial-intersect-point_01.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-index/rtree-index-join/spatial-intersect-point_02.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-index/rtree-index-join/spatial-intersect-point_03.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/disjunction-to-join.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/leftouterjoin-probe-pidx-with-join-btree-sidx_01_1.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/leftouterjoin-probe-pidx-with-join-btree-sidx_01_2.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/leftouterjoin-probe-pidx-with-join-btree-sidx_02_1.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/leftouterjoin-probe-pidx-with-join-btree-sidx_02_2.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-join_01.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-join_02.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-join_03.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_01.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_02.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_03.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_04.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_05.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_06.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join-multiindex.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join-multipred.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join_01.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join_02.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join_03.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join_04.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join_05.aql M
Change in asterixdb[master]: Fix open field CREATE INDEX syntax (AQL and SQLPP).
Hello Till Westmann, Jenkins, I'd like you to reexamine a change. Please visit https://asterix-gerrit.ics.uci.edu/1106 to look at the new patch set (#3). Change subject: Fix open field CREATE INDEX syntax (AQL and SQLPP). .. Fix open field CREATE INDEX syntax (AQL and SQLPP). Our CREATE INDEX syntax for open fields didn't match our semantics. Our semantics allow to-be-indexed open field(s) to be MISSING. We don't support (or offer :-)) tighter semantics than that. Our syntax didn't require creators to say this, but now it does: Old: CREATE INDEX myIdx on MyDSet(myTime: datetime) ENFORCED; New: CREATE INDEX myIdx on MyDSet(myTime: datetime?) ENFORCED; Have now addressed all of Till's comments (I think). Change-Id: I32bf8bc5ac1c0e6aa6744ca8f91a197311219814 --- M asterixdb/asterix-app/src/test/resources/metadata/queries/basic/meta16/meta16.1.ddl.aql M asterixdb/asterix-app/src/test/resources/metadata/queries/basic/meta17/meta17.1.ddl.aql M asterixdb/asterix-app/src/test/resources/metadata/queries/basic/meta24/meta24.1.ddl.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/meta/secondary_index-lojoin_with_meta-1.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/meta/secondary_index-nljoin_with_meta-1.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/meta/secondary_index-nljoin_with_meta-2.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/meta/secondary_index_with_meta-2.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-index/rtree-index-join/spatial-intersect-point_01.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-index/rtree-index-join/spatial-intersect-point_02.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-index/rtree-index-join/spatial-intersect-point_03.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/disjunction-to-join.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/leftouterjoin-probe-pidx-with-join-btree-sidx_01_1.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/leftouterjoin-probe-pidx-with-join-btree-sidx_01_2.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/leftouterjoin-probe-pidx-with-join-btree-sidx_02_1.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/leftouterjoin-probe-pidx-with-join-btree-sidx_02_2.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-join_01.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-join_02.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-join_03.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_01.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_02.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_03.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_04.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_05.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_06.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join-multiindex.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join-multipred.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join_01.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join_02.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join_03.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join_04.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join_05.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index/btree-secondary-33.aql M
Change in asterixdb[master]: Fix open field CREATE INDEX syntax (AQL and SQLPP).
Hello Jenkins, I'd like you to reexamine a change. Please visit https://asterix-gerrit.ics.uci.edu/1106 to look at the new patch set (#2). Change subject: Fix open field CREATE INDEX syntax (AQL and SQLPP). .. Fix open field CREATE INDEX syntax (AQL and SQLPP). Our CREATE INDEX syntax for open fields didn't match our semantics. Our semantics allow to-be-indexed open field(s) to be MISSING. We don't support (or offer :-)) tighter semantics than that. Our syntax didn't require creators to say this, but now it does: Old: CREATE INDEX myIdx on MyDSet(myTime: datetime) ENFORCED; New: CREATE INDEX myIdx on MyDSet(myTime: datetime?) ENFORCED; Have now addressed all of Till's comments (I think). Change-Id: I32bf8bc5ac1c0e6aa6744ca8f91a197311219814 --- M asterixdb/asterix-app/src/test/resources/metadata/queries/basic/meta16/meta16.1.ddl.aql M asterixdb/asterix-app/src/test/resources/metadata/queries/basic/meta17/meta17.1.ddl.aql M asterixdb/asterix-app/src/test/resources/metadata/queries/basic/meta24/meta24.1.ddl.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/meta/secondary_index-lojoin_with_meta-1.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/meta/secondary_index-nljoin_with_meta-1.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/meta/secondary_index-nljoin_with_meta-2.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/meta/secondary_index_with_meta-2.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-index/rtree-index-join/spatial-intersect-point_01.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-index/rtree-index-join/spatial-intersect-point_02.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-index/rtree-index-join/spatial-intersect-point_03.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/disjunction-to-join.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/leftouterjoin-probe-pidx-with-join-btree-sidx_01_1.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/leftouterjoin-probe-pidx-with-join-btree-sidx_01_2.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/leftouterjoin-probe-pidx-with-join-btree-sidx_02_1.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/leftouterjoin-probe-pidx-with-join-btree-sidx_02_2.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-join_01.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-join_02.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-join_03.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_01.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_02.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_03.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_04.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_05.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_06.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join-multiindex.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join-multipred.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join_01.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join_02.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join_03.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join_04.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join_05.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index/btree-secondary-33.aql M
Change in asterixdb[master]: ASTERIXDB-1186: fixed a composite primary index search issue.
Michael Carey has posted comments on this change. Change subject: ASTERIXDB-1186: fixed a composite primary index search issue. .. Patch Set 6: Code-Review+1 Since I'm a novice reviewer, I won't +2 it, but I would if I had more confidence. :-) -- To view, visit https://asterix-gerrit.ics.uci.edu/1094 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: comment Gerrit-Change-Id: I0f75229ea804a02e7cacd04f7269a4907668eab0 Gerrit-PatchSet: 6 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Taewoo KimGerrit-Reviewer: Jenkins Gerrit-Reviewer: Michael Carey Gerrit-Reviewer: Taewoo Kim Gerrit-Reviewer: Till Westmann Gerrit-Reviewer: Yingyi Bu Gerrit-HasComments: No
Change in asterixdb[master]: ASTERIXDB-1186: fixed a composite primary index search issue.
Michael Carey has posted comments on this change. Change subject: ASTERIXDB-1186: fixed a composite primary index search issue. .. Patch Set 6: Looked at the code and plans - looks good to me. (Got a jump start in person during a meeting today that helped a lot.) -- To view, visit https://asterix-gerrit.ics.uci.edu/1094 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: comment Gerrit-Change-Id: I0f75229ea804a02e7cacd04f7269a4907668eab0 Gerrit-PatchSet: 6 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Taewoo KimGerrit-Reviewer: Jenkins Gerrit-Reviewer: Michael Carey Gerrit-Reviewer: Taewoo Kim Gerrit-Reviewer: Till Westmann Gerrit-Reviewer: Yingyi Bu Gerrit-HasComments: No
Change in asterixdb[master]: ASTERIXDB-1186: fixed a composite primary index search issue.
Michael Carey has posted comments on this change. Change subject: ASTERIXDB-1186: fixed a composite primary index search issue. .. Patch Set 6: NOTE: A number of the (optimizer only) test cases affected by this change were previously WRONG! I.e., we had WRONG PLANS (as in correctness wrong, not just performance wrong) checked in as the expected results. I wonder how many other cases might be like that. Scary. I wonder if there's a need for an audit of the expected results in our optimizer test cases? -- To view, visit https://asterix-gerrit.ics.uci.edu/1094 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: comment Gerrit-Change-Id: I0f75229ea804a02e7cacd04f7269a4907668eab0 Gerrit-PatchSet: 6 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Taewoo KimGerrit-Reviewer: Jenkins Gerrit-Reviewer: Michael Carey Gerrit-Reviewer: Taewoo Kim Gerrit-Reviewer: Till Westmann Gerrit-Reviewer: Yingyi Bu Gerrit-HasComments: No
Change in asterixdb[master]: Change to create syntax for open indices - both for AQL and ...
Michael Carey has uploaded a new change for review. https://asterix-gerrit.ics.uci.edu/1106 Change subject: Change to create syntax for open indices - both for AQL and SQLPP. .. Change to create syntax for open indices - both for AQL and SQLPP. The following commits from your working branch will be included: commit 84e16861182dd2bb4de0b2e14eedfdf44941ae1b Author: Mike CareyDate: Tue Aug 23 10:57:32 2016 -0700 Changed open index creation syntax to require optionality indicator on to-be-indexed fields (to match semantics). commit bda12fc81fd9a800b87ebfa75fd527375f3cd4bd Author: Mike Carey Date: Fri Jul 29 17:51:15 2016 -0700 making optionality non-optional when creating an open index, part 1 Change-Id: I32bf8bc5ac1c0e6aa6744ca8f91a197311219814 --- M asterixdb/asterix-app/src/test/resources/metadata/queries/basic/meta16/meta16.1.ddl.aql M asterixdb/asterix-app/src/test/resources/metadata/queries/basic/meta17/meta17.1.ddl.aql M asterixdb/asterix-app/src/test/resources/metadata/queries/basic/meta24/meta24.1.ddl.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/meta/secondary_index-lojoin_with_meta-1.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/meta/secondary_index-nljoin_with_meta-1.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/meta/secondary_index-nljoin_with_meta-2.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/meta/secondary_index_with_meta-2.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-index/rtree-index-join/spatial-intersect-point_01.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-index/rtree-index-join/spatial-intersect-point_02.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-index/rtree-index-join/spatial-intersect-point_03.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/disjunction-to-join.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/leftouterjoin-probe-pidx-with-join-btree-sidx_01_1.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/leftouterjoin-probe-pidx-with-join-btree-sidx_01_2.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/leftouterjoin-probe-pidx-with-join-btree-sidx_02_1.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/leftouterjoin-probe-pidx-with-join-btree-sidx_02_2.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-join_01.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-join_02.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-join_03.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_01.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_02.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_03.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_04.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_05.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-composite-key-prefix-join_06.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join-multiindex.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join-multipred.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join_01.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join_02.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join_03.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join_04.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index-join/secondary-equi-join_05.aql M asterixdb/asterix-app/src/test/resources/optimizerts/queries/nested-open-index/btree-index/btree-secondary-33.aql M
Change in asterixdb[master]: Making the web UI language neutral :-)
Michael Carey has submitted this change and it was merged. Change subject: Making the web UI language neutral :-) .. Making the web UI language neutral :-) Change-Id: Ia1035066170b5da5ab6839e6989b46d72e6c89e2 Reviewed-on: https://asterix-gerrit.ics.uci.edu/1007 Reviewed-by: Till WestmannReviewed-by: Ian Maxon Sonar-Qube: Jenkins Tested-by: Jenkins Integration-Tests: Jenkins --- M asterixdb/asterix-app/src/main/resources/webui/querytemplate.html 1 file changed, 1 insertion(+), 1 deletion(-) Approvals: Ian Maxon: Looks good to me, approved Till Westmann: Looks good to me, approved Jenkins: Verified; No violations found; Verified diff --git a/asterixdb/asterix-app/src/main/resources/webui/querytemplate.html b/asterixdb/asterix-app/src/main/resources/webui/querytemplate.html index 9115b89..ea53616 100644 --- a/asterixdb/asterix-app/src/main/resources/webui/querytemplate.html +++ b/asterixdb/asterix-app/src/main/resources/webui/querytemplate.html @@ -208,7 +208,7 @@ Query - + -- To view, visit https://asterix-gerrit.ics.uci.edu/1007 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: merged Gerrit-Change-Id: Ia1035066170b5da5ab6839e6989b46d72e6c89e2 Gerrit-PatchSet: 2 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Michael Carey Gerrit-Reviewer: Ian Maxon Gerrit-Reviewer: Jenkins Gerrit-Reviewer: Michael Carey Gerrit-Reviewer: Till Westmann
Change in asterixdb[master]: Making the web UI language neutral :-)
Michael Carey has uploaded a new change for review. https://asterix-gerrit.ics.uci.edu/1007 Change subject: Making the web UI language neutral :-) .. Making the web UI language neutral :-) Change-Id: Ia1035066170b5da5ab6839e6989b46d72e6c89e2 --- M asterixdb/asterix-app/src/main/resources/webui/querytemplate.html 1 file changed, 1 insertion(+), 1 deletion(-) git pull ssh://asterix-gerrit.ics.uci.edu:29418/asterixdb refs/changes/07/1007/1 diff --git a/asterixdb/asterix-app/src/main/resources/webui/querytemplate.html b/asterixdb/asterix-app/src/main/resources/webui/querytemplate.html index 9115b89..ea53616 100644 --- a/asterixdb/asterix-app/src/main/resources/webui/querytemplate.html +++ b/asterixdb/asterix-app/src/main/resources/webui/querytemplate.html @@ -208,7 +208,7 @@ Query - + -- To view, visit https://asterix-gerrit.ics.uci.edu/1007 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: newchange Gerrit-Change-Id: Ia1035066170b5da5ab6839e6989b46d72e6c89e2 Gerrit-PatchSet: 1 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Michael Carey