- 
                Notifications
    
You must be signed in to change notification settings  - Fork 31
 
USE_DATETIME env var for filter behavior #443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
8330771    to
    d5c98f0      
    Compare
  
    dbb1831    to
    ad18cb9      
    Compare
  
    There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@YuriZmytrakov This is really useful. 1. changelog update. 2. we should probably have a test for this.
        
          
                CHANGELOG.md
              
                Outdated
          
        
      | - `STAC_INDEX_ASSETS` environment variable to allow asset serialization to be configurable. [#433](https://github.com/stac-utils/stac-fastapi-elasticsearch-opensearch/pull/433) | ||
| - Added the `ENV_MAX_LIMIT` environment variable to SFEOS, allowing overriding of the `MAX_LIMIT`, which controls the `?limit` parameter for returned items and STAC collections. [#434](https://github.com/stac-utils/stac-fastapi-elasticsearch-opensearch/pull/434) | ||
| - Updated the `format_datetime_range` function to support milliseconds. [#423](https://github.com/stac-utils/stac-fastapi-elasticsearch-opensearch/pull/423) | ||
| - Added `USE_DATETIME` environment variable behavior to set datetime filtering logic. [#443](https://github.com/stac-utils/stac-fastapi-elasticsearch-opensearch/pull/443) | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi. Any new changes need to be put under the Unreleased section as v6.3.0 has already been released.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jonhealy1 I have moved my changes to Unrealeased section. Thank you!
af1a390    to
    969e7a8      
    Compare
  
    
          
 Yes, we can do that.  | 
    
        
          
                CHANGELOG.md
              
                Outdated
          
        
      | 
               | 
          ||
| ## [Unreleased] | ||
| 
               | 
          ||
| - Added `USE_DATETIME` environment variable behavior to set datetime filtering logic. [#443](https://github.com/stac-utils/stac-fastapi-elasticsearch-opensearch/pull/443) | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a, ### Added, header above this entry.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done, thank you!
        
          
                README.md
              
                Outdated
          
        
      | | `STAC_ITEM_LIMIT` | Sets the environment variable for result limiting to SFEOS for the number of returned items and STAC collections. | `10` | Optional | | ||
| | `STAC_INDEX_ASSETS` | Controls if Assets are indexed when added to Elasticsearch/Opensearch. This allows asset fields to be included in search queries. | `false` | Optional | | ||
| | `ENV_MAX_LIMIT` | Configures the environment variable in SFEOS to override the default `MAX_LIMIT`, which controls the limit parameter for returned items and STAC collections. | `10,000` | Optional | | ||
| | `USE_DATETIME` | Configures the environment variable to control datetime filtering behavior. When `true`, searches by datetime field, and if datetime is `null` then by start/end datetime fields. When `false`, always searches only by start/end datetime fields. | true | Optional | | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to have a test for this new functionality
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added tests for the use_datetime variable (true/false) to verify changes in filter behavior.
e2b72de    to
    2132c43      
    Compare
  
    There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great. Tests are great, just the changelog issue to look at.
        
          
                CHANGELOG.md
              
                Outdated
          
        
      | 
               | 
          ||
| ### Added | ||
| 
               | 
          ||
| - Added `USE_DATETIME` environment variable behavior to set datetime filtering logic. [#443](https://github.com/stac-utils/stac-fastapi-elasticsearch-opensearch/pull/443) | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @YuriZmytrakov - this entry is still under the v6.3.0 section. It needs to be moved to the Unreleased section above. You will need to add an '### Added' header to the Unreleased section and move your pr entry there.
[Unreleased]
Changed
- updated 
numReturned&numMatchedfields in itemCollection return tonumberReturned&numberMatched. #446 
[v6.3.0] - 2025-09-16
Added
- Added 
USE_DATETIMEenvironment variable behavior to set datetime filtering logic. #443 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apologies, I was working on not the latest version, I have moved comment in changelog under Unreleased Added section: 3b36f72
d24d291    to
    3b36f72      
    Compare
  
    | 
           @YuriZmytrakov Looks like errors with Opensearch?  | 
    
5d99d46    to
    2528ea2      
    Compare
  
    - Added USE_DATETIME env var to control datetime filtering - USE_DATETIME=True (default): use existing logic that handles both datetime and start/end datetime fields - USE_DATETIME=False (default): use only start/end datetime fields for search
- test_use_datetime_true: Verify USE_DATETIME=true finds looks up by datetime, if null then by start/end datetime range - test_use_datetime_false: Verify USE_DATETIME=false only search items with start/end datetime values
e835a01    to
    804c52d      
    Compare
  
    | 
           @jonhealy1 I had to   | 
    
| 
           @YuriZmytrakov Do you know why it was failing? Did you change something in the new version?  | 
    
          
 Yes, I was not able to rebase this branch on the latest   | 
    
Related Issue(s):
#403
Description:
This PR introduces a new env var
USE_DATETIMEto control the datetime filtering behavior in the search.PR Checklist:
pre-commit run --all-files)make test)