No refelections set on this dataset, I’m planing using them later.
Currently I’m just playing with the Dremio SQL editor selecting the index.
I’ve created a new dataset with only one node of the cluster and still having the same issue
I’ll reinstall and see what happens.
Can you make sure you’re clicking Run as opposed to Preview. The Preview button may utilize caching as it’s designed to make it possible for users to curate/shape large datasets.
Yep, did that as well, no luck
I restarted Dremio and got a message asking to run
ALTER TABLE Kibana.“systemlog-c-2017.43”.systemlog REFRESH METADATA
After got this error:
Failure handling type. Dremio only supports a path to type mapping across all schema mappings. Dataset path Kibana.“systemlog-c-2017.43”.systemlog. Path to field segments. Declared Type segments::struct<toIata::varchar, marketingCarrier::varchar, timeOfArrival::timestamp, fromIata::varchar, timeOfDeparture::timestamp, operatingCarrier::varchar, flightNumber::varchar>. Observed Type segments::union<struct<toIata::varchar, marketingCarrier::varchar, timeOfArrival::timestamp, fromIata::varchar, timeOfDeparture::timestamp, operatingCarrier::varchar, flightNumber::varchar>, list<struct<toIata::varchar, marketingCarrier::varchar, timeOfArrival::timestamp, fromIata::varchar, timeOfDeparture::timestamp, operatingCarrier::varchar, flightNumber::varchar>>, struct<toIata::varchar, marketingCarrier::varchar, timeOfArrival::timestamp, fromIata::varchar, timeOfDeparture::timestamp, operatingCarrier::varchar, flightNumber::varchar>>
I have created a new dataset with just one node and I’m getting always the REFRESH METADATA error when running the query and old data with the preview.
UPDATE
After reinstalling I tested few queries:
SELECT MAX(“@timestamp”)
Returns correct date
Running (not preview) a query fails with the error above. Could it be caused by an structure change during this days?
Dremio only supports a path to type mapping across all schema mappings.
Does it means I have a mapping mistmatch between nodes?
Thanks
The Elastic data source settings including the “Advanced Settings”
General
Name
Kibana
Description
Hosts
Host
X.X.X.X
Port
9200
Add Host
Authentication
No Authentication
Pushdown Options
✔
Scripts enabled in Elasticsearch cluster
Advanced Options
Show hidden indices that start with a dot (.)
✔
Use the Painless scripting language when connecting to Elasticsearch 5.0+ (experimental)
✔
Query whitelisted hosts only
✔
Show _id column in elastic tables
Read Timeout (Seconds)
60
Scroll Timeout (Seconds)
300
Scroll Size
4000
Metadata Caching
Dataset Discovery
Fetch every
1
Hour(s)
Dataset Details
Fetch mode
Only Queried Datasets
Fetch every
1
Hour(s)
Expire after
3
Hour(s)
Connection Options
SSL enabled connecting to Elasticsearch cluster
Acceleration
Refresh Policy
Refresh every
1
Hour(s)
Expire after
3
Hour(s)
The mapping of the index if that can be shared
This can not be possible right now.Currently, AFAIK it’s giant!
Is “systemlog-c-2017.43”.systemlog” an ALIAS? Can you also remove and reattach the source if that is not a big hassle. Just trying to narrow down the issue.
Hi @balaji.ramaswamy,
Is not an alias, is an index. I have left only one node on the dataset to check if it was a problem with different configurations between nodes in the cluster but problem persist.
What do you mean by “remove and reattach” ? the alias?