Support geopoint type

[GumpacG]

Description

Supports geo_point by adding properties for lat and lon in order for Tableau to access locations.
This PR will only support the format {"lat": number, "lon": number}.
Geopoint will be treated as an ExprTupleValue to allow access to lat and lon properties.

Expect results on Tableau when opensearch-project#1793 is resolved:

Follow up work:

• Support Geopoint type in JDBC ([FEATURE] Support for geo_point type opensearch-project/sql-jdbc#99)
• Resolve [FEATURE] BI tools compliance with complex objects opensearch-project/sql#1793 in order for BI tools to use geopoint
• Support other formats of Geopoint

Check List

• New functionality includes testing.
  • All tests pass, including unit test, integration test and doctest
• New functionality has been documented.
  • New functionality has javadoc added
  • New functionality has user manual doc added
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[codecov]

Codecov Report

Merging #309 (cc54f39) into integ-geopoint (430d7a9) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@                 Coverage Diff                  @@
##             integ-geopoint     #309      +/-   ##
====================================================
- Coverage             97.42%   97.42%   -0.01%     
+ Complexity             4647     4645       -2     
====================================================
  Files                   408      408              
  Lines                 11526    11525       -1     
  Branches                839      841       +2     
====================================================
- Hits                  11229    11228       -1     
  Misses                  290      290              
  Partials                  7        7              

Flag	Coverage Δ
sql-engine	97.42% <100.00%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed	Coverage Δ
...h/sql/opensearch/data/type/OpenSearchDataType.java	100.00% <ø> (ø)
...l/opensearch/data/type/OpenSearchGeoPointType.java	100.00% <100.00%> (ø)
...l/opensearch/data/utils/OpenSearchJsonContent.java	100.00% <100.00%> (ø)
...search/data/value/OpenSearchExprGeoPointValue.java	100.00% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[MitchellGale]

Tested with:
An object with a latitude and longitude
A string in the “latitude,longitude” format
A geohash

found in https://opensearch.org/docs/2.3/opensearch/supported-field-types/geo-point/

LGTM.

[MitchellGale]

SQL plugin currently only supports the format :code:`{"lat": number, "lon": number}`. Can you add this to the PR description please

[MitchellGale]

Consider adding a test for lat issue and separate test for lon issue from opensearch/src/main/java/org/opensearch/sql/opensearch/data/utils/OpenSearchJsonContent.java.

[GumpacG]

We actually cant load non-number values in to lat and lon to OpenSearch. So integtests won't work. I believe this is just a fail safe for the valueFactory. There are unit tests for this I think that would be enough. Thoughts?

[Yury-Fridlyand]

Please, fix tests.

[Yury-Fridlyand]

Please, rebase or merge on upstream to fix CI