Skip to content
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

[BUG] "DATE_NANOS fieldName types are currently not supported." for join operation #3422

Open
peffis opened this issue Mar 13, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@peffis
Copy link

peffis commented Mar 13, 2025

What is the bug?
According to the supported types page it says that date_nanos type is supported. However, when I write a SELECT where I refer to a field with type "timestamp" I receive an exception in return saying that DATE_NANOS is not supported, like so

OpenSearchException({'error': {'reason': 'There was internal problem at backend', 'details': 'DATE_NANOS fieldName types are currently not supported.', 'type': 'IllegalArgumentException'}, 'status': 500})

The index in question was produced by Data Prepper writing trace information to OpenSearch. The query was a join that looked like this:

SELECT L.body,T.startTime FROM otel-v1-apm-span-000010 T JOIN mylogs L ON L.spanId=T.spanId;

, where "mylogs" is an index with log entries also written by Data Prepper, which has matching spanId and traceId information.

This does NOT happen for a simple non-join query like:

SELECT startTime FROM otel-v1-apm-span-000010;

, so strangely it seems like it is the join that triggers this exception to happen.

How can one reproduce the bug?
This can probably be done in simpler manners, but my method was to let Data Prepper write one index with trace information and one index with log information, and after that try a join based on spanId for instance, where you select the startTime from the trace as one of the fields.

What is the expected behavior?
It should just return the startTime, similar to how it is returned on a direct non-join query.

What is your host/environment?

  • OS: ubuntu linux
  • Version 24.04
  • Plugins OpenSearch SQL, OpenSearch Dashboard, OpenSearch

Do you have any screenshots?

Do you have any additional context?
Opensearch, Opensearch Dashboard and Data Prepper were installed with helm in kubernetes.
Versions were:
$ helm list -n tracestudy
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
data-prepper-release tracestudy 1 2025-03-12 08:07:10.940609 +0100 CET deployed data-prepper-0.3.1 2.8.0
opensearch-dashboard tracestudy 1 2025-03-03 09:18:38.3799 +0100 CET deployed opensearch-dashboards-2.28.0 2.19.1
opensearch-deployment tracestudy 1 2025-03-03 08:44:44.309739 +0100 CET deployed opensearch-2.32.0 2.19.

@peffis peffis added bug Something isn't working untriaged labels Mar 13, 2025
@LantaoJin LantaoJin added calcite calcite migration releated and removed untriaged calcite calcite migration releated labels Mar 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants