-
Notifications
You must be signed in to change notification settings - Fork 1.6k
questdb 9.0.2: invalid table name or alias #6058
Description
To reproduce
Run this simple query (it works in 8.3.3, stopped working on 9.0.0):
select distinct samples.sensor_id,sensors.apptype
from samples
inner join sensors on sensors.sensor_id = samples.sensor_id
;
ERROR: Invalid table name or alias
LINE 1: select distinct samples.sensor_id,sensors.apptype
^
Table definitions as following:
create table if not exists sensors (
-- sensor ID, UUID
sensor_id SYMBOL capacity 1000000 cache,
UUID SYMBOL capacity 1000000 cache,
-- app_instance_id LONG,
event_id INT,
condition_id INT,
-- enterprise
network_name SYMBOL,
-- building data
building_name SYMBOL,
building_description SYMBOL,
-- device data
device_name SYMBOL,
device_location SYMBOL,
device_area_code SYMBOL,
device_city SYMBOL,
device_address SYMBOL,
-- node data
node_serial_number SYMBOL,
node_name SYMBOL,
-- source (probe, FCC)
source SYMBOL,
apptype INT,
-- probe data
probe_description SYMBOL,
probe_address SYMBOL,
model_id INT,
feature SYMBOL,
feature_idx INT,
feature_description SYMBOL,
-- tag (probe/advanced monitoring)
tag SYMBOL,
-- timestamp is mandatory
ts TIMESTAMP
) timestamp (ts)
partition by day
wal;
create table if not exists samples (
sensor_id SYMBOL cache,
"sample" FLOAT,
ts TIMESTAMP
), index(sensor_id)
timestamp(ts)
partition by day
ttl 5 years
wal
;
QuestDB version:
9.0.2
OS, in case of Docker specify Docker and the Host OS:
Red Hat Enterprise Linux release 9.5 (Plow)
File System, in case of Docker specify Host File System:
xfs
Full Name:
Andrea Moretto
Affiliation:
HyperMatrix
Have you followed Linux, MacOs kernel configuration steps to increase Maximum open files and Maximum virtual memory areas limit?
- Yes, I have
Additional context
No response