OSDU Software issueshttps://community.opengroup.org/groups/osdu/-/issues2022-10-31T10:27:40Zhttps://community.opengroup.org/osdu/platform/data-flow/ingestion/opc-ua-ingestion/-/issues/4Write sample code to connect to Energyvue server using eclipse milo2022-10-31T10:27:40ZAshutosh KumarWrite sample code to connect to Energyvue server using eclipse miloWrite sample code to connect to energyvue server using eclipse milo
The OPC server endpoint is
opc.tcp://demo.energyvue.com:62546/EnergyVue/OpcServer
Preferred security is shown below and should be automatically adopted by the server ...Write sample code to connect to energyvue server using eclipse milo
The OPC server endpoint is
opc.tcp://demo.energyvue.com:62546/EnergyVue/OpcServer
Preferred security is shown below and should be automatically adopted by the server if you support it.
Mode: Sign & Encrypt
Policy: Aes256Sha256RsaPssAshutosh KumarAshutosh Kumarhttps://community.opengroup.org/osdu/platform/data-flow/ingestion/opc-ua-ingestion/-/issues/3Write/Explore Sample code to connect to Eclipse milo server using eclipse mil...2022-07-06T03:59:29ZAshutosh KumarWrite/Explore Sample code to connect to Eclipse milo server using eclipse milo sdkDownload eclipse milo sdk code and try to write and execute program to connect to Eclipse milo server
opc.tcp://milo.digitalpetri.com:62541/milo
Also try to connect Using:
1: Unified automation UAExpert
2: Using Eclipse milo sdk.Download eclipse milo sdk code and try to write and execute program to connect to Eclipse milo server
opc.tcp://milo.digitalpetri.com:62541/milo
Also try to connect Using:
1: Unified automation UAExpert
2: Using Eclipse milo sdk.Ashutosh KumarAshutosh Kumarhttps://community.opengroup.org/osdu/platform/data-flow/ingestion/opc-ua-ingestion/-/issues/2Explore the OPC UA client and server2022-07-06T03:59:50ZAshutosh KumarExplore the OPC UA client and server1: Explore OPC UA Client and server architecture.
2: Check the communication methods between them.1: Explore OPC UA Client and server architecture.
2: Check the communication methods between them.M14 - Release 0.17Ashutosh KumarAshutosh Kumarhttps://community.opengroup.org/osdu/platform/consumption/geospatial/-/issues/137Release - Document Docker requirement for Kubernetes2022-07-06T16:10:58ZJoel RomeroRelease - Document Docker requirement for KubernetesAs a GIS Analyst, I want to document Docker requirements for Kubernetes deployment.
Acceptance Criteria:
- Document results for future development
Note:
Do we have an Enterprise Docker license for OSDU? - Brian B
Need a Spike story for...As a GIS Analyst, I want to document Docker requirements for Kubernetes deployment.
Acceptance Criteria:
- Document results for future development
Note:
Do we have an Enterprise Docker license for OSDU? - Brian B
Need a Spike story for future implementation after MVPhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/62Release process does not follow general approach2023-03-24T19:22:10ZMikhail Piatliou (EPAM)Release process does not follow general approachThe pipelines for the `release` branches and `tags` https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/blob/v0.15.0/devops/osdu/cloud-providers/gcp.yml use reference ...The pipelines for the `release` branches and `tags` https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/blob/v0.15.0/devops/osdu/cloud-providers/gcp.yml use reference to the `master` branch in https://community.opengroup.org/osdu/platform/ci-cd-pipelines/-/tree/master/cloud-providers.
It is incorrect behavior since the service release/tags pipelines should have reference to the release/tags in ci-cd common pipelines accordingly.
For example, Partition service https://community.opengroup.org/osdu/platform/system/partition/-/blob/v0.15.1/.gitlab-ci.yml#L51.
The issue is valid for all CSPs.
Cc: @divido @Kateryna_Kurach @Oleksandr_KosseDaniel PerezDaniel Perezhttps://community.opengroup.org/osdu/platform/security-and-compliance/entitlements/-/issues/107Group name validation and email validation are not consistent2022-06-24T22:29:31ZAn NgoGroup name validation and email validation are not consistentWhen creating a group, group name is validated against expression: "^[A-Za-z0-9{}_.-]{3,128}$"
At the same time, when executing get members request, the email is validated
against expression: "^[A-Za-z0-9+_.-]{1,256}+@[A-Za-z0-9+_.-]{1,2...When creating a group, group name is validated against expression: "^[A-Za-z0-9{}_.-]{3,128}$"
At the same time, when executing get members request, the email is validated
against expression: "^[A-Za-z0-9+_.-]{1,256}+@[A-Za-z0-9+_.-]{1,256}$"
Such inconsistency caused existence of such group: {{new_creatordatagroup}}@some-partition.enterprisedata.cloud.some-domain.com, and members of such group could not be retrieved.https://community.opengroup.org/osdu/platform/system/file/-/issues/72File service - Compute and store properties such as filesize and checksum at ...2022-08-23T15:21:13ZDebasis ChatterjeeFile service - Compute and store properties such as filesize and checksum at the time of uploading fileCurrently, Data Loader is expected to provide this information manually. This can be error prone and can be missed.
cc - @Keith_Wall and @krveduru for informationCurrently, Data Loader is expected to provide this information manually. This can be error prone and can be missed.
cc - @Keith_Wall and @krveduru for informationhttps://community.opengroup.org/osdu/platform/system/dataset/-/issues/40Dataset service - Compute and store properties such as filesize and checksum ...2022-09-29T13:41:10ZDebasis ChatterjeeDataset service - Compute and store properties such as filesize and checksum at the time of uploading fileCurrently, Data Loader is expected to provide this information manually. This can be error prone and can be missed.
cc - @Keith_Wall and @krveduru for informationCurrently, Data Loader is expected to provide this information manually. This can be error prone and can be missed.
cc - @Keith_Wall and @krveduru for informationhttps://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics/witsml-parser/-/issues/60Implement missing fields following Wellbore Trajectory schema update2022-06-21T18:48:18Zetienne peyssonImplement missing fields following Wellbore Trajectory schema updateFollowing the WEllboare trajectory schema update (1.0.0 -> 1.1.0), we need to add the mapping for the following fields :
```
"AppliedOperations": [
"Example AppliedOperations"
],
"CompanyID": "namespace:master-data--Org...Following the WEllboare trajectory schema update (1.0.0 -> 1.1.0), we need to add the mapping for the following fields :
```
"AppliedOperations": [
"Example AppliedOperations"
],
"CompanyID": "namespace:master-data--Organisation:SomeUniqueOrganisationID:",
```M13 - Release 0.16https://community.opengroup.org/osdu/platform/data-flow/ingestion/opc-ua-ingestion/-/issues/1Exploring OPC-UA open source SDK2022-07-06T04:00:23ZChad LeongExploring OPC-UA open source SDKEvaluating different OPC-UA open-source client SDK options
1. Eclipse Milo
2. OPC UA client SDKEvaluating different OPC-UA open-source client SDK options
1. Eclipse Milo
2. OPC UA client SDKAshutosh KumarAshutosh Kumarhttps://community.opengroup.org/osdu/platform/system/indexer-service/-/issues/66Reindex API - performance, scalability and reliability issues2023-12-18T16:13:23ZNeelesh ThakurReindex API - performance, scalability and reliability issuesRecent issues on Schema/Search backend requires us to re-index significant number of kinds/indices. Here are specifics on these issue:
- M10 schema [hints changes](https://community.opengroup.org/osdu/data/data-definitions/-/blob/master/...Recent issues on Schema/Search backend requires us to re-index significant number of kinds/indices. Here are specifics on these issue:
- M10 schema [hints changes](https://community.opengroup.org/osdu/data/data-definitions/-/blob/master/E-R/ChangeReport.md#snapshot-2021-11-09-towards-m10) on Schema service.
- Geoshape queries are broken when Elasticsearch server upgraded from 7.8.1 --> 7.17.x (Confirmed by Elasticsearch Support team, public issue is not available)
Current implementation of Reindex API (per kind) has serious performance, scalability and reliability issues. It does not work at all for kind with few million records. This is blocking us from adopting M10 (now M11) schema updates. Following list summarizes issues with API:
- API throughput is pretty slow and it can only re-index 250K-300K records per hour. In case of partition with 100 million records, this can run over 2 weeks.
- It’s not resilient, if operation fails in the middle, we have to start over.
- There is no transparency for Reindex operation, we don’t know how much progress has been made.
In addition to above issues, we cannot recover Search service in Disaster recovery scenarios as well. In this case, we can use ReindexAll API which use Reindex API (per kind) behind the scene. We run into to all of above issues.https://community.opengroup.org/osdu/platform/system/schema-service/-/issues/107Have an IT for nested $ref version upgrade2022-08-24T11:29:09ZAbhishek Kumar (SLB)Have an IT for nested $ref version upgradeThere is no IT present to validate nested $ref version upgrade.There is no IT present to validate nested $ref version upgrade.Neha SardaNeha Sardahttps://community.opengroup.org/osdu/platform/system/schema-service/-/issues/106Make each IT test to run in isolation2022-08-24T11:28:19ZAbhishek Kumar (SLB)Make each IT test to run in isolationAs of today there are some test cases which depends on successful execution of previous testcase.
This should not be the case and each test-case should be able to execute independently.As of today there are some test cases which depends on successful execution of previous testcase.
This should not be the case and each test-case should be able to execute independently.Neha SardaNeha Sardahttps://community.opengroup.org/osdu/platform/system/schema-service/-/issues/105Remove unwanted logs from IT2022-12-09T13:39:36ZAbhishek Kumar (SLB)Remove unwanted logs from ITAs of today there are too many unwanted logs printed during IT execution which slows down the execution.As of today there are too many unwanted logs printed during IT execution which slows down the execution.Neha SardaNeha Sardahttps://community.opengroup.org/osdu/platform/system/storage/-/issues/130Storage PUT: setting a non-number value to a number attribute results in an e...2022-08-23T15:45:28ZAn NgoStorage PUT: setting a non-number value to a number attribute results in an empty 400 response (no error message)For example, given this payload. This was provided:
` "value": Infinity`
```
curl --location --request PUT 'https://domain.com/api/storage/v2/records' \
--header 'accept: application/json' \
--header 'data-partition-id: osdu' \
--hea...For example, given this payload. This was provided:
` "value": Infinity`
```
curl --location --request PUT 'https://domain.com/api/storage/v2/records' \
--header 'accept: application/json' \
--header 'data-partition-id: osdu' \
--header 'Content-Type: application/json' \
--header 'Authorization: <token>' \
--data-raw '[
{
"acl": {
"owners": [
"data.default.owners@domain.com"
],
"viewers": [
"data.default.viewers@domain.com"
]
},
"data": {
"ExtensionProperties": {
"osdu": {
"curvesProperties": [
{
"curveID": "CTEM_GPITF",
"properties": [
{
"name": "MEASURE-POINT-OFFSET",
"value": Infinity
}
]
}
]
}
}
},
"kind": "osdu:wks:work-product-component--WellLog:1.1.0",
"legal": {
"legaltags": [
"osdu-default-legal"
],
"otherRelevantDataCountries": [
"US"
]
}
}
]'
```
Reponse:
Empty 400
![image](/uploads/18749c6ea879c9c888a3c5c173288b23/image.png)https://community.opengroup.org/osdu/platform/system/storage/-/issues/128Data store location is not appended to legal tag ORDC of record2022-10-26T14:11:23ZAn NgoData store location is not appended to legal tag ORDC of recordUpon creating a record, the data store location/country is expected to be appended to the ORDC (Other relevant data countries) list.
This is not the current behavior.
```
"otherRelevantDataCountries": [
"VN"
]
```
Here, "VN"...Upon creating a record, the data store location/country is expected to be appended to the ORDC (Other relevant data countries) list.
This is not the current behavior.
```
"otherRelevantDataCountries": [
"VN"
]
```
Here, "VN" was provided when creating the record. Upon record creation, the system is supposed to append "US" (US environment partition), "BE" (EU) or "NL" (WEU), etc..https://community.opengroup.org/osdu/data/open-test-data/-/issues/80Add spatial information for TNO Well Log Records2022-06-10T15:49:09ZMichaelAdd spatial information for TNO Well Log RecordsThe manifest records for the TNO work-product-component--WellLog lack any Spatial fields. This prevents any spatialFilter queries from being done on the well logs. The location information should be provided for the trajectories when ava...The manifest records for the TNO work-product-component--WellLog lack any Spatial fields. This prevents any spatialFilter queries from being done on the well logs. The location information should be provided for the trajectories when available because this allows users to filter well logsby location on a large scale without having to link a well log to its parent Wellbore or Well.Keith WallKeith Wallhttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/issues/228[BUG] Swagger page could not be displayed2022-06-09T18:53:20ZRostislav Vatolinvatolinrp@gmail.com[BUG] Swagger page could not be displayedSwagger page could not be displayed after recent upgrade of springfox-boot-starter to 3.0.0 for partition service. AuthorizationPolicy for partition service requires fix.Swagger page could not be displayed after recent upgrade of springfox-boot-starter to 3.0.0 for partition service. AuthorizationPolicy for partition service requires fix.https://community.opengroup.org/osdu/platform/system/reference/unit-service/-/issues/39Unit service v3 Swagger misses information2022-08-23T15:53:53ZKateryna Kurach (EPAM)Unit service v3 Swagger misses informationUnit service v3 swagger misses grouping and description of the models.
Link to v3: https://community.opengroup.org/osdu/platform/system/reference/unit-service/-/blob/master/docs/v3/api_spec/unit_service_openapi_v3.json
Link to v2: https:...Unit service v3 swagger misses grouping and description of the models.
Link to v3: https://community.opengroup.org/osdu/platform/system/reference/unit-service/-/blob/master/docs/v3/api_spec/unit_service_openapi_v3.json
Link to v2: https://community.opengroup.org/osdu/platform/system/reference/unit-service/-/blob/master/docs/v2/api_spec/unit_service_openapi_v2.jsonhttps://community.opengroup.org/osdu/platform/system/search-service/-/issues/94Search needs to be case-sensitive to be consistent with Schema2022-08-23T15:19:05ZAn NgoSearch needs to be case-sensitive to be consistent with SchemaCurrently, Schema service is case sensitive. Therefore, schema osdu:document:well:1.0.0 and osdu:Document:Well:1.0.0 are different.
Search is case in-sensitive. Therefore, it treats these 2 schema to be the same.
Due to this inconsiste...Currently, Schema service is case sensitive. Therefore, schema osdu:document:well:1.0.0 and osdu:Document:Well:1.0.0 are different.
Search is case in-sensitive. Therefore, it treats these 2 schema to be the same.
Due to this inconsistency, this payload returns the wrong results, for example:
```
{
"kind":"osdu:document:well:1.0.0",
"query": "*"
}
```
Here, it will return results from both osdu:document:well:1.0.0 and osdu:Document:Well:1.0.0.