Search issueshttps://community.opengroup.org/osdu/platform/system/search-service/-/issues2024-01-08T12:17:56Zhttps://community.opengroup.org/osdu/platform/system/search-service/-/issues/140Tutorial: Search by kind Guidance2024-01-08T12:17:56ZThomas Gehrmann [slb]Tutorial: Search by kind Guidance# [Query by kind](https://community.opengroup.org/osdu/platform/system/search-service/-/blob/master/docs/tutorial/SearchService.md?ref_type=heads#query-by-kind)
The tutorial promotes searching for specific **_versions_** of schemas, whi...# [Query by kind](https://community.opengroup.org/osdu/platform/system/search-service/-/blob/master/docs/tutorial/SearchService.md?ref_type=heads#query-by-kind)
The tutorial promotes searching for specific **_versions_** of schemas, which is not a good idea. In recent milestones the number of minor schema versions as well as patch versions have grown considerably.
* The tutorial should recommend wildcards for minor and patch versions.
* Using specific schema versions in query by `kind` will cause serious trouble when data records are schema-migrated, updated or newly ingested using, e.g., the using the [preferred schema version recommendation (Schema Usage Guide)](https://community.opengroup.org/osdu/data/data-definitions/-/blob/master/Guides/Chapters/93-OSDU-Schemas.md#appendix-d5-schema-version-managementconfiguration).
CC @nthakur, @chadM23 - Release 0.26Thomas Gehrmann [slb]Thomas Gehrmann [slb]https://community.opengroup.org/osdu/platform/system/search-service/-/issues/132Follow-up from "Add filter to nested sort"2023-08-17T16:07:05ZMark ChanceFollow-up from "Add filter to nested sort"The following discussion from !535 should be addressed:
- [ ] @nthakur started a [discussion](https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/535#note_241458): (+2 comments)
> Will filter conte...The following discussion from !535 should be addressed:
- [ ] @nthakur started a [discussion](https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/535#note_241458): (+2 comments)
> Will filter context work for non-nested scenario? If it does, can you please update non-nested section as well? If it does not, then we should add this in limitation documentation.M20 - Release 0.23Mark ChanceMark Chancehttps://community.opengroup.org/osdu/platform/system/search-service/-/issues/122Enhance documentation for multi-kind search feature2023-05-25T09:06:07ZAn NgoEnhance documentation for multi-kind search featureIn multi-kind search, note the behavior when the index of any kind does not exist.
Previously, we returned a 200 with 0 result. New behavior is to return the results for the valid indices.
(Do we list the kinds that failed?)
Also docum...In multi-kind search, note the behavior when the index of any kind does not exist.
Previously, we returned a 200 with 0 result. New behavior is to return the results for the valid indices.
(Do we list the kinds that failed?)
Also document on length limit, best practice, workaround, etc.M18 - Release 0.21https://community.opengroup.org/osdu/platform/system/search-service/-/issues/32[Question] What is the proper mechanism for searching by version?2023-03-09T18:15:53ZAlan Henson[Question] What is the proper mechanism for searching by version?Asking on behalf of one of my teams:
**Scenario**: If we query the search service for a record with a version that does not exist, the version that does exist is returned back. Our expectation is that zero results should be returned bac...Asking on behalf of one of my teams:
**Scenario**: If we query the search service for a record with a version that does not exist, the version that does exist is returned back. Our expectation is that zero results should be returned back from that query. Please refer to the search request below:
```
{
“kind”: “opendes:wks:work-product-component--LogCurve:1.0.0",
“query”: “id:\“opendes:work-product-component--LogCurve:ABDCQF01-48731\“, version:1615825387766997”
}
```
However, if we query the search service with the nonexistent version as a separate query, no versions will be returned. This is the behavior we are expecting. Please see the below request as an example:
```
{
“kind”: “opendes:wks:work-product-component--LogCurve:1.0.0”,
“query”: “id:\“opendes:work-product-component--LogCurve:ABDCQF01-48731\“”,
“query”: “version:1615825387766997”
}
```
**Questions**:
Which way is the correct way to query for a specific version number? If it’s the first option, is it expected that the existing version will always be returned regardless of what version is provided in the query?
Because the storage service seems to [overwrite outdated versions](https://community.opengroup.org/osdu/platform/system/storage/-/issues/58), will the user only have knowledge about the most recent version at any given time?
When providing an `id` value in a reference property, should we always reference the latest version with the `:` suffix? A reference to a specific version doesn’t seem usable as that version may be overwritten in the future based on observed behavior in the overwritten version issue linked above.ethiraj krishnamanaiduChris Zhangethiraj krishnamanaidu