From 91a242d4e0add18e7fccbc5297182b3ea98b9d03 Mon Sep 17 00:00:00 2001
From: Yauheni_Lesnikau <ylesnikau@slb.com>
Date: Wed, 18 Jan 2023 10:27:48 +0100
Subject: [PATCH] update os-core-common version in azure module to enable
enableExtendedRange flag
---
provider/search-azure/pom.xml | 1 +
.../src/main/resources/application.properties | 2 +
.../query/singlecluster/RunTest.java | 2 +-
.../singlecluster/SingleClusterQuery.feature | 238 ++++++++++++++++++
4 files changed, 242 insertions(+), 1 deletion(-)
create mode 100644 testing/integration-tests/search-test-azure/src/test/resources/features/query/singlecluster/SingleClusterQuery.feature
diff --git a/provider/search-azure/pom.xml b/provider/search-azure/pom.xml
index 192b47ec8..0585c0385 100644
--- a/provider/search-azure/pom.xml
+++ b/provider/search-azure/pom.xml
@@ -56,6 +56,7 @@
<azure-core.version>1.31.0</azure-core.version>
<azure-security-keyvault-keys.version>4.4.6</azure-security-keyvault-keys.version>
<azure-security-keyvault-secrets.version>4.4.6</azure-security-keyvault-secrets.version>
+ <osdu.oscorecommon.version>0.19.0-rc6</osdu.oscorecommon.version>
</properties>
<dependencyManagement>
diff --git a/provider/search-azure/src/main/resources/application.properties b/provider/search-azure/src/main/resources/application.properties
index 68f49b3ae..2a1ed0a6d 100644
--- a/provider/search-azure/src/main/resources/application.properties
+++ b/provider/search-azure/src/main/resources/application.properties
@@ -89,3 +89,5 @@ service.policy.enabled=true
service.policy.endpoint=${policy_service_endpoint}
policy.cache.timeout=5
service.policy.id=${service_policy_id:osdu.partition["%s"].search}
+
+validation.spatial.longitude.enableExtendedRange=true
diff --git a/testing/integration-tests/search-test-azure/src/test/java/org/opengroup/osdu/step_definitions/query/singlecluster/RunTest.java b/testing/integration-tests/search-test-azure/src/test/java/org/opengroup/osdu/step_definitions/query/singlecluster/RunTest.java
index 6508c5ff6..21205b2c1 100644
--- a/testing/integration-tests/search-test-azure/src/test/java/org/opengroup/osdu/step_definitions/query/singlecluster/RunTest.java
+++ b/testing/integration-tests/search-test-azure/src/test/java/org/opengroup/osdu/step_definitions/query/singlecluster/RunTest.java
@@ -21,7 +21,7 @@ import org.junit.runner.RunWith;
@RunWith(Cucumber.class)
@CucumberOptions(
- features = "classpath:features/query/singlecluster/Query.feature",
+ features = "classpath:features/query/singlecluster/SingleClusterQuery.feature",
glue = {"classpath:org.opengroup.osdu.step_definitions/query/singlecluster"},
plugin = {"pretty", "junit:target/cucumber-reports/TEST-query-sc.xml"})
public class RunTest {
diff --git a/testing/integration-tests/search-test-azure/src/test/resources/features/query/singlecluster/SingleClusterQuery.feature b/testing/integration-tests/search-test-azure/src/test/resources/features/query/singlecluster/SingleClusterQuery.feature
new file mode 100644
index 000000000..52373c492
--- /dev/null
+++ b/testing/integration-tests/search-test-azure/src/test/resources/features/query/singlecluster/SingleClusterQuery.feature
@@ -0,0 +1,238 @@
+Feature: Search with different queries
+ To allow a user to find his data quickly, search should offer multiple ways to search data.
+
+ Background:
+ Given the schema is created with the following kind
+ | kind | schemaFile |
+ | tenant1:search<timestamp>:test-data--Integration:1.0.1 | records_1 |
+ | tenant1:search<timestamp>:test-data2--Integration:1.0.2 | records_2 |
+ | tenant1:well<timestamp>:test-data3--Integration:1.0.3 | records_4 |
+
+ Scenario Outline: Ingest records for the given kind
+ When I ingest records with the <recordFile> with <acl> for a given <kind>
+ Examples:
+ | kind | recordFile | acl |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | "records_1" | "data.default.viewers@tenant1"|
+ | "tenant1:search<timestamp>:test-data2--Integration:1.0.2" | "records_2" | "data.default.viewers@tenant1"|
+ | "tenant1:well<timestamp>:test-data3--Integration:1.0.3" | "records_4" | "data.default.viewers@tenant1" |
+ Scenario Outline: Search data in a given kind
+ When I send <query> with <kind>
+ And I limit the count of returned results to <limit>
+ And I set the offset of starting point as <offset>
+ And I set the fields I want in response as <returned_fields>
+ And I send request to tenant <tenant>
+ Then I should get in response <count> records with <returned_fields>
+
+ Examples:
+ | tenant | kind | query | limit | offset | returned_fields | count |
+ | "tenant1" | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | "data.OriginalOperator:OFFICE4" | None | None | All | 1 |
+ | "tenant1" | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | None | 0 | None | NULL | 3 |
+ | "tenant1" | "tenant1:search<timestamp>:test-data2--Integration:1.0.2" | None | 0 | None | NULL | 3 |
+ | "tenant1" | "tenant1:search<timestamp>:test-data--Integration:1.0.1,tenant1:search<timestamp>:test-data2--Integration:1.0.2" | None | 0 | None | NULL | 6 |
+ | "tenant1" | ["tenant1:search<timestamp>:test-data--Integration:1.0.1", "tenant1:search<timestamp>:test-data2--Integration:1.0.2"] | None | 0 | None | NULL | 6 |
+ ######################################Range Query test cases##########################################################################
+ | "tenant1" | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | "data.Rank:{1 TO 3}" | None | None | id,index | 1 |
+ | "tenant1" | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | "data.Rank:[10 TO 20]" | None | None | All | 1 |
+ | "tenant1" | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | "data.Rank:>=2" | None | None | All | 2 |
+ | "tenant1" | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | "data.Established:{* TO 2012-01-01}" | None | None | All | 2 |
+ #####################################Text Query test cases###########################################################################
+ | "tenant1" | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | "OSDU" | None | None | All | 3 |
+ | "tenant1" | "tenant1:search<timestamp>:test-data2--Integration:1.0.2" | "data.OriginalOperator:OFFICE6" | None | None | All | 1 |
+ | "tenant1" | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | ""OFFICE2" \| OFFICE3" | None | None | All | 1 |
+ | "tenant1" | "tenant1:search<timestamp>:test-data2--Integration:1.0.2" | "data.Well\*:(Data Lake Cloud)" | None | None | All | 3 |
+
+ Scenario Outline: Search data in a given a kind with invalid inputs
+ When I send <query> with <kind>
+ And I limit the count of returned results to <limit>
+ And I set the offset of starting point as <offset>
+ And I send request to tenant <tenant>
+ Then I should get <response_code> response with reason: <reponse_type>, message: <response_message> and errors: <errors>
+
+ Examples:
+ | tenant | kind | query | limit | offset | response_code | reponse_type | response_message | errors |
+ | "tenant1" | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | None | -1 | None | 400 | "Bad Request" | "Invalid parameters were given on search request" | "'limit' must be equal or greater than 0" |
+ | "tenant1" | "invalid" | None | 1 | None | 400 | "Bad Request" | "Invalid parameters were given on search request" | "Not a valid record kind format. Found: invalid" |
+ | "tenant1" | "tenant1:search<timestamp>:test-data--Integration:1.0.1,,tenant1:search<timestamp>:test-data2--Integration:1.0.2" | None | 1 | None | 400 | "Bad Request" | "Invalid parameters were given on search request" | "Not a valid record kind format. Found: tenant1:search<timestamp>:test-data--Integration:1.0.1,,tenant1:search<timestamp>:test-data2--Integration:1.0.2" |
+ | "tenant1" | 123456789 | None | 1 | None | 400 | "Bad Request" | "Invalid parameters were given on search request" | "Not a valid record kind type. Found: 123456789" |
+ | "tenant1" | [] | None | 1 | None | 400 | "Bad Request" | "Invalid parameters were given on search request" | "Record kind can't be null or empty. Found: []" |
+ | "tenant1" | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | None | 1 | -1 | 400 | "Bad Request" | "Invalid parameters were given on search request" | "'offset' must be equal or greater than 0" |
+ | "tenant2" | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | None | None | None | 401 | "Access denied" | "The user is not authorized to perform this action" | "" |
+
+ Scenario Outline: Search data across the kinds with bounding box inputs
+ When I send <query> with <kind>
+ And I apply geographical query on field <field>
+ And define bounding box with points (<top_left_latitude>, <top_left_longitude>) and (<bottom_right_latitude>, <bottom_right_longitude>)
+ Then I should get in response <count> records
+
+ Examples:
+ | kind | query | field | top_left_latitude | top_left_longitude | bottom_right_latitude | bottom_right_longitude | count |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | None | "data.Location" | 45 | -100 | 0 | 0 | 2 |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | None | "data.Location" | 45 | -80 | 0 | 0 | 0 |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | "data.OriginalOperator:OFFICE4" | "data.Location" | 45 | -100 | 0 | 0 | 1 |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | "data.OriginalOperator:OFFICE4" | "data.Location" | 10 | -100 | 0 | 0 | 0 |
+
+ Scenario Outline: Search data across the kinds with invalid bounding box inputs
+ When I send <query> with <kind>
+ And I apply geographical query on field <field>
+ And define bounding box with points (<top_left_latitude>, <top_left_longitude>) and (<bottom_right_latitude>, <bottom_right_longitude>)
+ Then I should get <response_code> response with reason: <reponse_type>, message: <response_message> and errors: <errors>
+
+ Examples:
+ | kind | query | field | top_left_latitude | top_left_longitude | bottom_right_latitude | bottom_right_longitude | response_code | reponse_type | response_message | errors |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | "data.OriginalOperator:OFFICE4" | "data.Location" | 0 | 0 | 0 | 0 | 400 | "Bad Request" | "Invalid parameters were given on search request" | "top latitude cannot be the same as bottom latitude: 0.0 == 0.0" |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | "data.OriginalOperator:OFFICE4" | "data.Location" | 0 | -100 | -10 | -100 | 400 | "Bad Request" | "Invalid parameters were given on search request" | "left longitude cannot be the same as right longitude: -100.0 == -100.0" |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | "data.OriginalOperator:OFFICE4" | "data.Location" | 10 | -100 | 10 | 0 | 400 | "Bad Request" | "Invalid parameters were given on search request" | "top latitude cannot be the same as bottom latitude: 10.0 == 10.0" |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | "data.OriginalOperator:OFFICE4" | "data.Location" | 45 | -100 | -95 | 0 | 400 | "Bad Request" | "Invalid parameters were given on search request" | "'latitude' value is out of the range [-90, 90]" |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | "data.OriginalOperator:OFFICE4" | "data.Location" | 0 | -100 | 10 | 0 | 400 | "Bad Request" | "Invalid parameters were given on search request" | "top corner is below bottom corner: 0.0 vs. 10.0" |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | "data.OriginalOperator:OFFICE4" | "data.Location" | None | None | 0 | 0 | 400 | "Bad Request" | "Invalid parameters were given on search request" | "Invalid payload" |
+ | "tenant1:search<timestamp>:*:*" | None | "officeAddress" | 45 | -100 | 0 | 0 | 400 | "Bad Request" | "failed to find geo field [officeAddress]" | "" |
+
+ Scenario Outline: Search data across the kinds with distance inputs
+ When I send <query> with <kind>
+ And I apply geographical query on field <field>
+ And define focus coordinates as (<latitude>, <longitude>) and search in a <distance> radius
+ Then I should get in response <count> records
+
+ Examples:
+ | kind | query | field | latitude | longitude | distance | count |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | "Under development" | "data.Location" | 0 | 0 | 20000000 | 3 |
+ | "tenant1:search<timestamp>:*:*" | "TEXAS OR TX" | "data.Location" | 45 | -100 | 20000000 | 2 |
+
+ Scenario Outline: Search data across the kinds with invalid distance inputs
+ When I send <query> with <kind>
+ And I apply geographical query on field <field>
+ And define focus coordinates as (<latitude>, <longitude>) and search in a <distance> radius
+ Then I should get <response_code> response with reason: <reponse_type>, message: <response_message> and errors: <errors>
+
+ Examples:
+ | kind | query | field | latitude | longitude | distance | response_code | reponse_type | response_message | errors |
+ | "tenant1:search<timestamp>:*:*" | "OFFICE - 2" | "data.Location" | -45 | -400 | 1000 | 400 | "Bad Request" | "Invalid parameters were given on search request" | "'longitude' value is out of the range [-360, 360]" |
+ | "tenant1:search<timestamp>:*:*" | "TEXAS OR USA" | "data.Location" | -95 | -100 | 1000 | 400 | "Bad Request" | "Invalid parameters were given on search request" | "'latitude' value is out of the range [-90, 90]" |
+ | "tenant1:search<timestamp>:*:*" | "Harris" | "ZipCode" | -45 | -400 | 1000 | 400 | "Bad Request" | "Invalid parameters were given on search request" | "'longitude' value is out of the range [-360, 360]" |
+ | "tenant1:search<timestamp>:*:*" | "Harris" | "ZipCode" | 4 | 2 | 0 | 400 | "Bad Request" | "Invalid parameters were given on search request" | "'distance' must be greater than 0" |
+
+ Scenario Outline: Search data across the kinds
+ When I send <query> with <kind>
+ And I limit the count of returned results to <limit>
+ And I set the offset of starting point as <offset>
+ And I set the fields I want in response as <returned_fields>
+ And I send request to tenant <tenant>
+ Then I should get in response <count> records
+
+ Examples:
+ | tenant | kind | query | limit | offset | returned_fields | count |
+ | "tenant1" | "tenant1:search<timestamp>:*:*" | None | 1 | None | All | 1 |
+ | "tenant1" | "tenant1:search<timestamp>:*:*" | None | None | 2 | All | 4 |
+ | "tenant1" | "tenant1:search<timestamp>:*:*" | None | None | None | Country | 6 |
+ | "tenant1" | "tenant1:search<timestamp>:*:*" | "OSDU OFFICE*" | None | None | All | 6 |
+ | "tenant1" | "tenant1:search<timestamp>:*:*" | "SCHLUM OFFICE" | None | None | All | 6 |
+ | "tenant1" | "tenant1:search<timestamp>:*:*" | ""SCHLUM OFFICE"" | None | None | All | 0 |
+ | "tenant1" | "tenant1:search<timestamp>:*:*" | "data.Country:USA" | None | None | All | 2 |
+ | "tenant1" | "tenant1:search<timestamp>:*:*" | "TEXAS AND OFFICE3" | None | None | All | 1 |
+ | "tenant1" | "tenant1:search<timestamp>:*:*" | "data.OriginalOperator:OFFICE5 OR OFFICE2" | None | None | All | 2 |
+ | "tenant1" | "tenant1:search<timestamp>:*:*" | "data.OriginalOperator:STI OR HT" | None | None | All | 0 |
+ | "tenant1" | "tenant1:search<timestamp>:*:*" | "_exists_:data.Basin" | None | None | All | 4 |
+ | "tenant1" | "tenant1:search<timestamp>:*:*" | "data.Well\*:"Data Lake Cloud"" | None | None | All | 5 |
+
+
+ Scenario Outline: Search data across the kinds with bounding box inputs
+ When I send <query> with <kind>
+ And I apply geographical query on field <field>
+ And define bounding box with points (<top_left_latitude>, <top_left_longitude>) and (<bottom_right_latitude>, <bottom_right_longitude>)
+ Then I should get in response <count> records
+
+ Examples:
+ | kind | query | field | top_left_latitude | top_left_longitude | bottom_right_latitude | bottom_right_longitude | count |
+ | "tenant1:search<timestamp>:*:*" | None | "data.Location" | 45 | -100 | 0 | 0 | 3 |
+ | "tenant1:search<timestamp>:*:*" | None | "data.Location" | 10 | -100 | 0 | 0 | 0 |
+
+ Scenario Outline: Search data across the kinds with geo polygon inputs
+ When I send <query> with <kind>
+ And define geo polygon with following points <points_list>
+ And I apply geographical query on field <field>
+ Then I should get in response <count> records
+ Examples:
+ | kind | query | field | points_list | count |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | None | "data.Location" | (26.12362;-112.226716) , (26.595873;-68.457186) , (52.273184;-93.593904) | 2 |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | None | "data.Location" | (33.201112;-113.282863) , (33.456305;-98.269744) , (52.273184;-93.593904) | 0 |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | "OFFICE4" | "data.Location" | (26.12362;-112.226716) , (26.595873;-68.457186) , (52.273184;-93.593904) | 1 |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | None | "data.Location" | (14.29056;72.18936) , (22.13762;72.18936) , (22.13762;77.18936) , (14.29056;77.18936) , (14.29056;72.18936) | 1 |
+
+ Scenario Outline: Search data across the kinds with invalid geo polygon inputs
+ When I send <query> with <kind>
+ And define geo polygon with following points <points_list>
+ And I apply geographical query on field <field>
+ Then I should get <response_code> response with reason: <response_type>, message: <response_message> and errors: <errors>
+
+ Examples:
+ | kind | query | field | points_list | response_code | response_type | response_message | errors |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | None | "data.Location" | (26.595873;-68.457186) , (52.273184;-93.593904) | 400 | "Bad Request" | "Invalid parameters were given on search request" | "too few points defined for geo polygon query" |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | None | "data.Location" | (516.595873;-68.457186) , (52.273184;-94.593904) , (95.273184;-93.593904) | 400 | "Bad Request" | "Invalid parameters were given on search request" | "'latitude' value is out of the range [-90, 90]" |
+
+ Scenario Outline: Search data and sort the results with the given sort fields and order
+ When I send <query> with <kind>
+ And I want the results sorted by <sort>
+ Then I should get records in right order first record id: <first_record_id>, last record id: <last_record_id>
+ Examples:
+ | kind | query | sort | first_record_id | last_record_id |
+ | "tenant1:search<timestamp>:*:*" | None | {"field":["data.OriginalOperator","data.WellType"],"order":["ASC", "ASC"]} | "tenant1:search<timestamp>:1" | "tenant1:search<timestamp>:2.0.0:3" |
+ | "tenant1:search<timestamp>:*:*" | None | {"field":["id"],"order":["DESC"]} | "tenant1:search<timestamp>:3" | "tenant1:search<timestamp>:1" |
+ | "tenant1:search<timestamp>:*:*" | None | {"field":["namespace","data.Rank"],"order":["ASC","DESC"]} | "tenant1:search<timestamp>:3" | "tenant1:search<timestamp>:2.0.0:1" |
+ | "tenant1:well<timestamp>:test-data3--Integration:1.0.3" | None | {"field":["nested(data.VerticalMeasurements, VerticalMeasurement, min)"],"order":["ASC"]} | "tenant1:well<timestamp>:2" | "tenant1:well<timestamp>:1" |
+ | "tenant1:well<timestamp>:test-data3--Integration:1.0.3" | None | {"field":["nested(data.FacilityOperators, TerminationDateTime, min)"],"order":["DESC"]} | "tenant1:well<timestamp>:2" | "tenant1:well<timestamp>:1" |
+
+ Scenario Outline: Search data in a given kind with invalid sort field
+ When I send <query> with <kind>
+ And I want the results sorted by <sort>
+ Then I should get <response_code> response with reason: <response_type>, message: <response_message> and errors: <errors>
+
+ Examples:
+ | kind | query | sort | response_code | response_type | response_message | errors |
+ | "tenant1:search<timestamp>:*:*" | None | {"field":[],"order":["ASC"]} | 400 | "Bad Request" | "Invalid parameters were given on search request" | "'sort.field' can not be null or empty" |
+ | "tenant1:search<timestamp>:*:*" | None | {"field":["id"],"order":[]} | 400 | "Bad Request" | "Invalid parameters were given on search request" | "'sort.order' can not be null or empty" |
+ | "tenant1:search<timestamp>:*:*" | None | {"field":["id","data.Rank"],"order":["DESC"]} | 400 | "Bad Request" | "Invalid parameters were given on search request" | "'sort.field' and 'sort.order' size do not match" |
+ | "tenant1:search<timestamp>:*:*" | None | {"field":["id"],"order":[null]} | 400 | "Bad Request" | "Invalid parameters were given on search request" | "Not a valid order option. It can only be either 'ASC' or 'DESC'" |
+
+ Scenario Outline: Search data in a given kind with different searchAs modes
+ When I send <query> with <kind>
+ And I want to search as owner <is_owner>
+ Then I should get in response <count> records when searchAs owner is <is_owner>
+
+ Examples:
+ | kind | query | is_owner | count |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | None | true | 3 |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | None | false | 3 |
+ | "tenant1:search<timestamp>:test-data2--Integration:1.0.2" | None | false | 3 |
+ | "tenant1:search<timestamp>:*:*" | None | false | 6 |
+ | "tenant1:search<timestamp>:*:*" | "OFFICE4" | true | 1 |
+ | "tenant1:search<timestamp>:*:*" | None | None | 6 |
+
+ Scenario Outline: Search data in a given kind with aggregateBy field
+ When I send <query> with <kind>
+ And I want to aggregate by <aggregateBy>
+ Then I should get <count> unique values
+
+ Examples:
+ | kind | query | aggregateBy | count |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | None | "namespace" | 1 |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | None | "type" | 1 |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | "OFFICE4" | "data.Rank" | 1 |
+ | "tenant1:search<timestamp>:test-data--Integration:1.0.1" | None | "data.Rank" | 3 |
+ | "tenant1:well<timestamp>:test-data3--Integration:1.0.3" | None | "nested(data.VerticalMeasurements, VerticalMeasurement)" | 2 |
+ | "tenant1:well<timestamp>:test-data3--Integration:1.0.3" | nested(data.VerticalMeasurements, (VerticalMeasurement:(<15))) | "nested(data.VerticalMeasurements, VerticalMeasurement)" | 1 |
+
+ Scenario Outline: Search data in a given kind with nested queries
+ When I send <query> with <kind>
+ And I send request to tenant <tenant>
+ Then I should get in response <count> records
+
+ Examples:
+ | tenant | kind | query | count |
+ | "tenant1" | "tenant1:well<timestamp>:test-data3--Integration:1.0.3" | "nested(data.VerticalMeasurements, (VerticalMeasurement:(>15.0) AND EffectiveDateTime:[2010-02-13T09:13:15.55+0000 TO 2021-02-13T09:13:15.55+0000]))" | 1 |
+ | "tenant1" | "tenant1:well<timestamp>:test-data3--Integration:1.0.3" | "nested(data.VerticalMeasurements, (VerticalMeasurement:(>15.0) OR EffectiveDateTime:[2010-02-13T09:13:15.55+0000 TO 2021-02-13T09:13:15.55+0000]))" | 2 |
+ | "tenant1" | "tenant1:well<timestamp>:test-data3--Integration:1.0.3" | "data.Source:"Example*" AND nested(data.VerticalMeasurements, (VerticalMeasurementDescription:"Example*"))" | 2 |
+ | "tenant1" | "tenant1:well<timestamp>:test-data3--Integration:1.0.3" | "data.Source:"Example*" AND nested(data.VerticalMeasurements, (VerticalMeasurementDescription:"Example*")) AND data.FacilityName:"NOT EXISTING NAME"" | 0 |
+ | "tenant1" | "tenant1:well<timestamp>:test-data3--Integration:1.0.3" | "nested(data.VerticalMeasurements, (VerticalMeasurement:(<15)))" | 1 |
+ | "tenant1" | "tenant1:well<timestamp>:test-data3--Integration:1.0.3" | "nested(data.FacilityOperators, (TerminationDateTime:[2023 TO 2026] AND EffectiveDateTime:[* TO 2021])) NOT nested(data.VerticalMeasurements, (VerticalMeasurement:(>20000)))" | 1 |
+ | "tenant1" | "tenant1:well<timestamp>:test-data3--Integration:1.0.3" | "nested(data.FacilityOperators, (TerminationDateTime:[2023 TO 2026])) OR nested(data.VerticalMeasurements, (VerticalMeasurement:(>15)))" | 2 |
+ | "tenant1" | "tenant1:well<timestamp>:test-data3--Integration:1.0.3" | "nested(data.VerticalMeasurements, (VerticalMeasurementID:"Other*" AND VerticalMeasurement:(<30)))" | 1 |
--
GitLab