OSDU Software issueshttps://community.opengroup.org/groups/osdu/-/issues2022-11-28T14:10:32Zhttps://community.opengroup.org/osdu/platform/system/file/-/issues/63Preloadfilepath & ExtensionProperties removed from file Metadata API2022-11-28T14:10:32Zivar SoerheimPreloadfilepath & ExtensionProperties removed from file Metadata APIDuring ingestion of file metadata under /files/metadata using POST command the Preloadfilepath and ExtensionProperties are not persisted when returning the record post ingest.
This seems like strange behaviour to me. I would like to ei...During ingestion of file metadata under /files/metadata using POST command the Preloadfilepath and ExtensionProperties are not persisted when returning the record post ingest.
This seems like strange behaviour to me. I would like to either understand why this happens, or extend the file metadata api so these properties are not removed.
This is the workflow:
1. Get Signed URL for upload
2. Upload file using signed URL
3. Upload file metadata using file api (this returns ID of created record and can be searched in storage)
4. Refer to this ID when creating well log record or any other record
The problem with this workflow is that:
- PreloadFilePath and ExtensionProperties are removed from the record during metadata uploadhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-cpp-lib/-/issues/13Add a possibility to work with Anthos/MinIO.2023-03-30T16:59:36ZYan Sushchynski (EPAM)Add a possibility to work with Anthos/MinIO.Hello!
We implemented Seismic DMS for `Anthos` environment with MinIO as a storage backend. MinIO implementation works with `s3` and mostly follows AWS implementation.
For `sdutil`, all we needed was overriding a single method of `AwsS...Hello!
We implemented Seismic DMS for `Anthos` environment with MinIO as a storage backend. MinIO implementation works with `s3` and mostly follows AWS implementation.
For `sdutil`, all we needed was overriding a single method of `AwsStorageService` service; we just added MinIO endpoint.
(https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-sdutil/-/merge_requests/50/diffs#316b48789c54e1de5292718db6abac8856b6cec3_0_48)
The problem is that `Open VDS` and `Open ZGY` convertors use `seismic-cpp-lib` and there is no way to access MinIO storage to manipulate files.
I found that the library gets the information about Cloud provider for choosing a storage class from the response header of Seismic
(https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-cpp-lib/-/blob/master/src/src/lib/cloud/SeismicStore.cc#L704).
This value is taken from `CLOUDPROVIDER` env var of Seismic deployment. As our `CLOUDPROVIDER`'s value is `anthos`, `seismic-cpp-lib` chooses `GcsAccessorStorage`(
https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-cpp-lib/-/blob/master/src/src/lib/cloud/Storage.cc#L172)
What we need:
1. Choose `AwsStorage` if cloud provider is `anthos`;
1. Possibility to override AWS's Endpoint URL with the environmental variable's value.
SDMS MR:
https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/322
Thanks.
fyi: @Siarhei_Khaletski @jorgenhttps://community.opengroup.org/osdu/platform/pre-shipping/-/issues/247AWS - Unable to generate access tokens2022-08-23T12:47:10ZMichaelAWS - Unable to generate access tokensI am unable to use the "Auth/Get Tokens" and "Auth/Update Tokens" postman requests https://osduonaws-artifacts.s3.amazonaws.com/postman/AWS+OSDU+R3+API+Collections.postman_collection.json to generate access tokens. This was previously wo...I am unable to use the "Auth/Get Tokens" and "Auth/Update Tokens" postman requests https://osduonaws-artifacts.s3.amazonaws.com/postman/AWS+OSDU+R3+API+Collections.postman_collection.json to generate access tokens. This was previously working a few days ago.
When I try to call "Auth/Get Tokens" I see the following error message:
![image](/uploads/00636b7ba52ed3d7a36cf6326f9efc22/image.png)
I see the following message in the postman console:
GET https://osr3m10-561735291427.auth.us-east-2.amazoncognito.com/error?error=invalid_request&client_id=7r2r9b7vpegec4pj3kueu5i81t
When I try to call the "Auth/Update Tokens" request, I see the following error message:
Status: 400 Bad Request
```
{
"error": "invalid_client"
}
```https://community.opengroup.org/osdu/platform/data-flow/ingestion/osdu-ingestion-lib/-/issues/5Limit not set for Search API query2022-03-16T15:32:18Zharshit aggarwalLimit not set for Search API queryWe are not setting the limit in the search query while searching for external references and hence it defaults to 10 (i.e. maximum 10 records will be returned from search api) Therefore the integrity check is failing if total records are...We are not setting the limit in the search query while searching for external references and hence it defaults to 10 (i.e. maximum 10 records will be returned from search api) Therefore the integrity check is failing if total records are greater than 10
Code Reference - https://community.opengroup.org/osdu/platform/data-flow/ingestion/osdu-ingestion-lib/-/blob/master/osdu_ingestion/libs/search_record_ids.py#L113
If we see currently there is no limit setM10 Patch - Release 0.13 patchhttps://community.opengroup.org/osdu/platform/pre-shipping/-/issues/241Issue with data returned from search service - trying to verify unit conversi...2022-08-23T12:47:14ZTaylor GraberIssue with data returned from search service - trying to verify unit conversion (Azure)I am trying to verify that the unit conversion is working appropriately when using CSV ingestion. When I check the data via the storage service, I see data in input units and can verify it's working properly. When I try to retrieve data ...I am trying to verify that the unit conversion is working appropriately when using CSV ingestion. When I check the data via the storage service, I see data in input units and can verify it's working properly. When I try to retrieve data records via the search service, it does not show the appropriate data so that we can confirm it is in SI units. I've included the results from M9 running the same query as seen in the uploads in the test results folder run by Debasis. This has the data as expected to verify results.
**Current results from M10 testing**
POST https://{{SEARCH_HOST}}/query
{
"kind": "opendes:wellbore:testEntity_730993:0.0.1",
"query": "id: \"opendes:testEntity_730993:wellbore-U1AxNjE2MjM0MTQyNTMx\"",
"limit": 10
}
{
"results": [
{
"createTime": "2022-03-02T13:12:52.193Z",
"kind": "opendes:wellbore:testEntity_730993:0.0.1",
"authority": "opendes",
"namespace": "opendes:wellbore",
"legal": {
"legaltags": [
"opendes-Test-Legal-Tag-7112912"
],
"otherRelevantDataCountries": [
"US"
],
"status": "compliant"
},
"createUser": "60c4b736-2aa4-4889-88a0-d50503d63de7",
"source": "wellbore",
"acl": {
"viewers": [
"data.default.viewers@opendes.contoso.com"
],
"owners": [
"data.default.owners@opendes.contoso.com"
]
},
"id": "opendes:testEntity_730993:wellbore-U1AxNjE2MjM0MTQyNTMx",
"type": "testEntity_730993",
"version": 1646226771801651,
"tags": {
"dataflowId": "test-dataflowid-proxy"
}
}
],
"aggregations": null,
"totalCount": 1
}
**Results from M9 testing**
POST https://{{SEARCH_HOST}}/query
Body
{
"kind": "opendes:debasis:testEntity_123425:1.0.0",
"query": "id: \"opendes:testEntity_123425:9886b54d038d4a9fb96af65092882750\"",
"limit": 10
}
Response
{
"results": [
{
"data": {
"TVD": 6312.7128,
"PERMIT_NUMBER": "SMP-09995",
"WELLBORE_NAME": null,
"CRS": "GCS_North_American_1927",
"LONGUITUDE": -89.66605738,
"WELLBORE_NUMBER": null,
"STATE": "NORTHERN GULF OF MEXICO",
"CLASS": "NEW FIELD WILDCAT",
"WELLBORE_SHAPE": "DIRECTIONAL",
"FORMATION_AT_TD": "MIOCENE LOWER",
"STATUS": "DRY & ABANDONED",
"COUNTRY": "USA",
"MD": 6388.608,
"ORIGINAL_OPERATOR": "SCHLUMBERGER",
"BASIN": "AT",
"EPSG_CODE": "4267.12",
"COUNTY": "ATWATER VALLEY",
"UNIT_SYSTEM": "English",
"UWI": "SP4358449212881",
"FIELD": "ATWATER VLLY B 8",
"ELEVATION": 25.606248000000004,
"OPERATOR": "SCHLUMBERGER",
"LEASE": "SMP G09995",
"LATITUDE": 27.85011793,
"ELEVATION_REF": "KB"
},
"kind": "opendes:debasis:testEntity_123425:1.0.0",
"source": "debasis",
"acl": {
"viewers": [
"data.default.viewers@opendes.contoso.com"
],
"owners": [
"data.default.viewers@opendes.contoso.com"
]
},
"type": "testEntity_123425",
"version": 1638830079687502,
"tags": {
"dataflowId": "test-dataflowid-proxy"
},
"createTime": "2021-12-06T22:34:40.614Z",
"authority": "opendes",
"namespace": "opendes:debasis",
"legal": {
"legaltags": [
"opendes-Test-Legal-Tag-9679576"
],
"otherRelevantDataCountries": [
"US"
],
"status": "compliant"
},
"createUser": "60c4b736-2aa4-4889-88a0-d50503d63de7",
"id": "opendes:testEntity_123425:9886b54d038d4a9fb96af65092882750"
}
],
"aggregations": null,
"totalCount": 1
}Saravana Kumar RajendranSaravana Kumar Rajendranhttps://community.opengroup.org/osdu/platform/system/reference/unit-service/-/issues/33Unit Conversion does not support converting value directly2022-08-30T14:18:18Zlifei liuUnit Conversion does not support converting value directlyUnit Conversion API does not support converting the value from one unit to another directly, e.g., converting 5ft to m. It supports retrieving conversion factors for two units, but leaves the calculation implementation to the user.
Fo...Unit Conversion API does not support converting the value from one unit to another directly, e.g., converting 5ft to m. It supports retrieving conversion factors for two units, but leaves the calculation implementation to the user.
For example there are three attributes “fromCRS”, “toCRS”, “Points” in CRS conversion so that the user can make one call to convert the coordinate from NAD27 to WGS84. To be comparable, it would make more sense to have a similar API for unit conversion including “fromUnit”, “toUnit”, “**value**” so that the user can get the converted result in one call.
cc: @debasischttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/46Write System Maintenance guide2022-08-23T13:29:50ZGreg HarrisWrite System Maintenance guideWrite System Maintenance guide to support handover of DDMS loader.Write System Maintenance guide to support handover of DDMS loader.Niall McDaidNiall McDaidhttps://community.opengroup.org/osdu/platform/system/sdks/common-python-sdk/-/issues/12Refactor/create Python SDK's ConfigManagers to work with Airflow config2022-10-18T11:09:14ZKateryna Kurach (EPAM)Refactor/create Python SDK's ConfigManagers to work with Airflow configThis is a follow-up for: https://community.opengroup.org/osdu/platform/system/sdks/common-python-sdk/-/merge_requests/58
Previously GCP team made the effort to decouple the term `Airflow` with Python SDK. We suggest to you create a new `...This is a follow-up for: https://community.opengroup.org/osdu/platform/system/sdks/common-python-sdk/-/merge_requests/58
Previously GCP team made the effort to decouple the term `Airflow` with Python SDK. We suggest to you create a new `ConfigManager` class at `osdu-airflow-lib` repository and specify your environment configuration.M14 - Release 0.17harshit aggarwalharshit aggarwalhttps://community.opengroup.org/osdu/platform/pre-shipping/-/issues/188Some requests in Well Delivery postman collection fail, because of hard code ...2022-08-23T12:47:17ZKamlesh TodaiSome requests in Well Delivery postman collection fail, because of hard code values.Use the provided collection with five use cases (UC1-UC5) and define the following variable to match the environment
SchemasURL = https://osdu-ship.msft-osdu-test.org/api/schema-service/v1/schema
welldeliveryURL = https://osdu-ship.msft...Use the provided collection with five use cases (UC1-UC5) and define the following variable to match the environment
SchemasURL = https://osdu-ship.msft-osdu-test.org/api/schema-service/v1/schema
welldeliveryURL = https://osdu-ship.msft-osdu-test.org/api/well-delivery
schemaHost = https://osdu-ship.msft-osdu-test.org
apisHost = https://osdu-ship.msft-osdu-test.org
dataPartitionID data-partition-id value e.g. opendes for azure
aclViewers data.default.viewers@{{data-partition-id}}{{domain}} e.g. for azure data.default.viewers@opendes.contoso.com
aclOwners data.default.owners@{{data-partition-id}}{{domain}} data.default.owners@opendes.contoso.com
legalTags pick any legal tag value in your environment opendes-public-usa-dataset-7643990
bearerToken assign value of access_token from the refresh token request
Once the expected environment was defined the collection ran fine with the following results
Requests that failed - status return was not successful.
UC1 well_activity_programs_specific_version_get_by_well
GET {{welldeliveryURL}}/wellActivityPrograms/v1/by_well/welldemo2/1638220411920
version value is hardcoded.
Response: 404 Not Found
UC2 activity_plans_by_well
GET {{welldeliveryURL}}/activityPlans/v1/by_well/welldemo1
mismatch between the ids (UC1 create well and UC2 get activity plans by well)
Response: 404 Not Found
UC3 query_BHArun_by_well
POST {{welldeliveryURL}}/query/v1/by_well/bhaRun:batch
Response: 404 Not Found
{
"message": "Could not find BHA run with wellbore id: wellbodemo2"
}
UC3 query_wellboreTrajectory_by_well
POST {{welldeliveryURL}}/query/v1/by_well/wellboreTrajectory:batch
Response: 404 Not Found
{
"message": "Could not find wellbore with well id: welldemo1"
}
UC4 holeSection_by_wellbore
GET {{welldeliveryURL}}/holeSections/v1/by_wellbore/wellboredemo02
Response: 404 Not Found
{
"message": "Not found wellbore segments with wellbore id :wellboredemo02"
}
GET {{welldeliveryURL}}/bhaRuns/v1/by_holeSection/holesectiondemo3
Response: 404 Not Found
{
"message": "Not found planned BHA runs with wellbore segment id :holesectiondemo3"
}
UC5 well_activity_programs_version_reference_tree
GET {{welldeliveryURL}}/wellActivityPrograms/v1/reference_tree/by_well/welldemo2/1638305706168
{
"message": "Could not find specific well activity program with well id: welldemo2 well activity program version : 1638305706168"
}
version value is hardcoded.
Response: 404 Not FoundM9 - Release 0.12Andrei IonescuAndrei Ionescuhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/41Rename 'lasloader' package and any associated references in repo2022-01-17T11:10:47ZNiall McDaidRename 'lasloader' package and any associated references in repoRelated to #32
Now the repo has been renamed to 'data loader' it would make sense to rename the package from 'lasloader' to something else.
There are lots of other references to specifically LAS throughout the repo ('lasloader' and 'la...Related to #32
Now the repo has been renamed to 'data loader' it would make sense to rename the package from 'lasloader' to something else.
There are lots of other references to specifically LAS throughout the repo ('lasloader' and 'lascli' being the most obvious) - these would also all need to be changed to remain consistent.
Things to do:
* Rename source code folders (packages)
* Rename lascli filename.
* Update the build and publish pipeline
* Fix comments in code.
* Update documentation.
* Test it all still works.Greg HarrisGreg Harrishttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/40lascli ingest wellbore command errors out when running against a folder conta...2022-08-23T13:29:51ZStephen Gallantlascli ingest wellbore command errors out when running against a folder containing multiple LAS filesFor example:
lascli ingest wellbore -p "C:\folder_containing_many_LAS_files" -c config.json -t token
Will error like:
Type List cannot be instantiated; use list() insteadFor example:
lascli ingest wellbore -p "C:\folder_containing_many_LAS_files" -c config.json -t token
Will error like:
Type List cannot be instantiated; use list() insteadNiall McDaidNiall McDaidhttps://community.opengroup.org/osdu/platform/system/search-service/-/issues/73ADR: Search data across multiple kinds in one search2023-06-23T08:08:59ZZhibin MaiADR: Search data across multiple kinds in one search## Status
- [X] Proposed
- [x] Under review
- [x] Approved
- [ ] Retired
## Context & Scope
It is quite common for users or applications to search data across multiple kinds in one search. In OSDU search, each kind is mapped to one inde...## Status
- [X] Proposed
- [x] Under review
- [x] Approved
- [ ] Retired
## Context & Scope
It is quite common for users or applications to search data across multiple kinds in one search. In OSDU search, each kind is mapped to one index. That means that users may need to search data across multi-indices in Elasticsearch. Elasticsearch supports search across multi-indices by specifying either index names as wildcard or a list of index names.
Currently, OSDU search only expose the wildcard solution (e.g. "kind": "\*:\*:\*:\*") to support search across multi-indices.
There may be hundreds of kinds if not thousands in one tenant data partition. We found that using wildcard to search across multi-indices introduces significant overhead on performance as comparing with a list of index names. The more indices in Elasticsearch, the bigger overhead could be introduced. The attached diagram shows our observation:
![image](/uploads/e84ac4851dd5d19c280b75e4b602d3ad/image.png)
## Trade-off Analysis
Here is the relevant API spec: https://community.opengroup.org/osdu/platform/system/search-service/-/blob/master/search-core/src/main/java/org/opengroup/osdu/search/api/SearchApi.java
Without introducing new field in the search API, we propose to concatenate the index (kind) names with comma in the existing “kind” property, e.g.
``````````````````````````
e.g. I have kinds in the system
a:b:c:d
a:e:c:d
a:f:c:d
a:g:c:d
I want to search keyword "well" against only 2 kinds
a:b:c:d
a:e:c:d
today I can only do this by forming a query
{
“kind”: "a:*:c:d”,
“query”: “(\"kind\": \"a:b:c:d\" OR \"kind\": \"a:e:c:d\") AND well”
}
This still makes my query slower because the search is performed against all indexes the wildcard matches i.e.
a:b:c:d
a:e:c:d
a:f:c:d
a:g:c:d
even though I know I only want to search against 2 of the indexes. The proposed solution will allow me to change this to
{
“kind”: “a:b:c:d,a:e:c:d”,
"query": "well"
}
Making my query easier to write and potentially a lot more performant as it targets ony the indexes I want to search against
``````````````````````````
Here are the Pros and Cons of the proposal:
| Pros| Cons|
| ------ | ------ |
| - Non-breaking change. No API change required. | - Not following the json pattern to code multiple items |
| - It is consistent with Elasticsearch's pattern on coding multi-indices for search. | |
| - Change only on "Common Code" in both "OSDU Core Common" and "Search Service". | |
## Decision
The proposal is a non-breaking change. Its implementation is pretty simple and safe. Prototype of the implementation in OSDU Core Common and Search Service can be found in MRs:
- [Change on Core Common](https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/127)
- [Change on Search service](https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/190)
## Consequences
This is a non-breaking change but with big performance gain when searching across multiple indices.M11 - Release 0.14Zhibin MaiZhibin Mai2022-01-14https://community.opengroup.org/osdu/platform/system/file/-/issues/51Update swagger documentation for end point "downloadURL"2022-09-29T13:29:51ZDebasis ChatterjeeUpdate swagger documentation for end point "downloadURL"Please check here -
https://community.opengroup.org/osdu/platform/system/file/-/blob/master/docs/file-service_openapi.yaml
GET {{FILE_HOST}}/files/{{FILE_ID}}/**downloadURL**
Swagger documentation shows **DownloadURL**
cc - @harshit2...Please check here -
https://community.opengroup.org/osdu/platform/system/file/-/blob/master/docs/file-service_openapi.yaml
GET {{FILE_HOST}}/files/{{FILE_ID}}/**downloadURL**
Swagger documentation shows **DownloadURL**
cc - @harshit283 for informationM14 - Release 0.17Shrikant GargShrikant Garghttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/34Missing PATH entry2022-08-23T13:29:51ZChad LeongMissing PATH entryReported by Stephen Gallant from Katalyst.
On install, it did give me several warnings on missing PATH entry to:
C:\Users\user\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\S...Reported by Stephen Gallant from Katalyst.
On install, it did give me several warnings on missing PATH entry to:
C:\Users\user\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\Scripts
But runs ok after adding this to PATH.Stephen GallantNiall McDaidStephen Gallanthttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/33No module named 'colorama'. User has to manually install that package separat...2021-12-01T10:28:26ZChad LeongNo module named 'colorama'. User has to manually install that package separately.Issue reported by Stephen Gallant from Katalyst.
After installing lascli, an errored out with: No module named 'colorama'. So I installed that separately, then it worked.
The module should be included as part of the package.Issue reported by Stephen Gallant from Katalyst.
After installing lascli, an errored out with: No module named 'colorama'. So I installed that separately, then it worked.
The module should be included as part of the package.Niall McDaidNiall McDaidhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/well-delivery/well-delivery/-/issues/5Need to create an endpoint that would return Well Delivery DDMS version2022-02-22T18:54:14ZKateryna Kurach (EPAM)Need to create an endpoint that would return Well Delivery DDMS versionWe need to provide an endpoint that will return the versioning info. Information for other services: https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/issues/47We need to provide an endpoint that will return the versioning info. Information for other services: https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/issues/47https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/well-delivery/well-delivery/-/issues/4Structure of Well, Wellbore records as created by Well Planning DDMS Domain API2021-12-20T21:49:26ZDebasis ChatterjeeStructure of Well, Wellbore records as created by Well Planning DDMS Domain APII found this example from Dev team's Postman Collection. As you can see this is different from standard Well wks V1.0.0 where information such as District, Operator, Spud Date are handled differently.
The concern is that - are we going ...I found this example from Dev team's Postman Collection. As you can see this is different from standard Well wks V1.0.0 where information such as District, Operator, Spud Date are handled differently.
The concern is that - are we going to have two types of "Well" record in OSDU Data Platform - one using standard V1.0.0 wks (as created by Manifest Ingestion, WITSML Parser etc.) and another structure using V3.0.0 if created from Well Planning DDMS Domain API?
PUT https://wd-osdu-api-qa.azurewebsites.net/api/well-delivery/storage/v1/well
Body
```
{
"id": "namespace:master-data--Well:well01",
"kind": "slb:wd-schema:Well:3.0.0",
"legal": {
"legaltags": [
"slb-osdu-dev-sis-internal-hq-public-usa-dataset-1"
],
"otherRelevantDataCountries": [
"US"
]
},
"acl": {
"owners": [
"data.default.viewers@slb-osdu-dev-sis-internal-hq.enterprisedata.cloud.slb-ds.com"
],
"viewers": [
"data.default.viewers@slb-osdu-dev-sis-internal-hq.enterprisedata.cloud.slb-ds.com"
]
},
"data": {
"Name": "well12345",
"NameLegal": "legal12345",
"NumLicense": "LIC12345",
"District": "Mildland",
"Operator": "BP",
"DTimSpud": "2020-01-01T01:01:01Z",
"ExistenceKind": "namespace:reference-data--ExistenceKind:planned:"
}
}
```https://community.opengroup.org/osdu/platform/system/search-service/-/issues/70Improve bad request response messages2022-03-09T10:22:47ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comImprove bad request response messagesRelated to https://community.opengroup.org/osdu/platform/system/search-service/-/issues/57
In case the query does not match with the actual structure of the index mapping, ElasticSearch can provide a detailed message that can help a us...Related to https://community.opengroup.org/osdu/platform/system/search-service/-/issues/57
In case the query does not match with the actual structure of the index mapping, ElasticSearch can provide a detailed message that can help a user to understand that query or mapping should be refactored. For example, `nested` query running for properties that are not nested in elasticsearch:
~~~
{
"kind": "{{data-partition-id}}:wks:master-data--Well:*.*.*",
"query": "nested(data.NameAliases, (AliasName:\"L10-14\" AND AliasNameTypeID:\"osdu:reference-data--AliasNameType:WELL_NAME:\"))"
}
~~~
Elasticsearch will respond with such message:
~~~
{
"error": {
"root_cause": [{
"type": "query_shard_exception",
"reason": "failed to create query: [nested] failed to find nested object under path [data.NameAliases]",
"index_uuid": "XVFuNDNAQvqrdeAlhykBYw",
"index": "odesprod-wks-master-data--well-1.0.0"
}
],
"type": "search_phase_execution_exception",
"reason": "all shards failed",
"phase": "query",
"grouped": true,
"failed_shards": [{
"shard": 0,
"index": "odesprod-wks-master-data--well-1.0.0",
"node": "vozOfr32RhSgpm7dCXzp0g",
"reason": {
"type": "query_shard_exception",
"reason": "failed to create query: [nested] failed to find nested object under path [data.NameAliases]",
"index_uuid": "XVFuNDNAQvqrdeAlhykBYw",
"index": "odesprod-wks-master-data--well-1.0.0",
"caused_by": {
"type": "illegal_state_exception",
"reason": "[nested] failed to find nested object under path [data.NameAliases]"
}
}
}
]
},
"status": 400
}
~~~
But for Search service users this message will be suppressed, and they will receive such not descriptive response:
~~~
{
"code": 400,
"reason": "Bad Request",
"message": "Invalid parameters were given on search request"
}
~~~
We need to improve `bad request` response messages, and transfer `elasticsearch` reason to users, this will simplify understanding the current data structure (that can be complicated).<br/>
Example response:
~~~
{
"code": 400,
"reason": "Bad Request",
"message": "failed to create query: [nested] failed to find nested object under path [data.NameAliases]"
}
~~~M10 - Release 0.13Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRostislav Dublin (EPAM)Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/93Imposible to install openvds module on Mac2022-07-21T13:09:53ZMateusz GeislerImposible to install openvds module on MacOn MacBook Pro (Intel processor) with python 3.7 I'm not able to install openvds module.
` pip install openvds
ERROR: Could not find a version that satisfies the requirement openvds (from versions: none)
ERROR: No matching distributi...On MacBook Pro (Intel processor) with python 3.7 I'm not able to install openvds module.
` pip install openvds
ERROR: Could not find a version that satisfies the requirement openvds (from versions: none)
ERROR: No matching distribution found for openvds
`https://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/24Capability to update an existing welllog with recognized curve families2021-10-25T14:45:47ZGreg HarrisCapability to update an existing welllog with recognized curve familiesAs a user I want to be able to update my existing welllog with recognized curve families.
To do this the id field (welllog id) of the record will need to be populated and sent as part of the post request.
This is an extension of [Issue...As a user I want to be able to update my existing welllog with recognized curve families.
To do this the id field (welllog id) of the record will need to be populated and sent as part of the post request.
This is an extension of [Issue 12](https://community.opengroup.org/osdu/platform/data-flow/data-loading/wellbore-ddms-las-loader/-/issues/12)Niall McDaidNiall McDaid