TLDR Ilya encountered errors while using OpenObserve. Ashish suggested using the dev image and provided instructions to clean up data. After implementing the solution, the errors were resolved.
Hi Ilya..this is a bug in current release
you can use dev image to proceed or we would make a release next week with fixes
public.ecr.aws/zinclabs/openobserve-dev:v0.4.7-155f766
Can you try this image
Ashish gonna try rn
Also..if possible clean up existing data
ingest data & test
Ashish could you please led me on how can I clean minio storage while using Helm-deployed openobserve?
do you have MinIO Client (mc)
you can use that to mc rm --force --recursive myminio/mybucket/*
Actually, you can use the UI delete the stream.
oh.. my bucket is empty so looks like something is misconfigured
it will auto delete data in storage.
from Left Menu --> Streams
it will list call your streams
delete the ones you want to cleanup
Updated to aforementioned version, ingested some logs, the error now is: ```"Arrow error: Json error: failed to parse \"unknown\" as Int64"```
this is during ingestion?
this is single node deployment right?
in openobserv dir you should have /data/ dir
can you please clean up that as well
that’s helm k8s deployment with minio
that error appears while searching logs (`/api/default/_search?type=logs`)
delete the cluster & delete PV named like data-zo1-openobserve-ingester-0
since your wal has corrupted data
you are facing this issue
Ilya
Fri, 09 Jun 2023 12:32:14 UTCHey guys! I just set up OpenObserve as our production logging system, and it’s pretty neat! I’m glad to see another cool Rust development. Now, I’m encountering two errors while trying to execute a SELECT * from logs query: ```"External error: Arrow error: Json error: failed to parse 18432951799850641000 as Int64"``` ```"Arrow error: Json error: expected string got false"``` It seems like something under the hood is attempting to convert our log entries to a specified schema, but the logs are not strictly typed. Is there any workaround for this issue?