Hi,
This is because the written data type is not compatible with the filter
constructed in TsFileRead.
I fixed this bug in this PR [1].
[1] https://github.com/apache/incubator-iotdb/pull/378
Best,
--
Jialin Qiao
School of Software, Tsinghua University
乔嘉林
清华大学 软件学院
> -原始邮件-
> 发件人:
Hi,
I've been working on JIRA issue [IOTDB-190 switch to ANTLR v4] these days.
I implemented the SQL parsing module. However, it seems that the parsing
efficiency reduces a lot when using ANTLR v4.
It turns out that RuleContext.getText() is frequently called, which takes more
than 90% of
Yuan Tian created IOTDB-202:
---
Summary: Bug in example module
Key: IOTDB-202
URL: https://issues.apache.org/jira/browse/IOTDB-202
Project: Apache IoTDB
Issue Type: Bug
Reporter: Yuan
Hi,
I think we can follow what Tian Jiang said to check whether KairosDB
considering it as a Long rather than a Float.
By the way, as Jialin and Julian said, I think it is ok if we print 0.0 for
Float 0.
Best,
---
Xiangdong Huang
School of Software, Tsinghua
Jialin Qiao created IOTDB-203:
-
Summary: A new result set format
Key: IOTDB-203
URL: https://issues.apache.org/jira/browse/IOTDB-203
Project: Apache IoTDB
Issue Type: New Feature
Hi,
As described in this issue, a new result set format is wanted by users. I'd
like to open a discussion here.
For simplicity, I refer this format "time, root.sg1.d1.s1, root.sg1.d2.s1" to
wide table, and "time, deviceId, s1" as narrow table.
This issue is not only about how to organize the
Hi Jialin,
perhaps one question about "wanted by users" means (as I didn’t see anything on
the list).
How do these users get in contact with you?
Julian
Am 07.09.19, 04:29 schrieb "Jialin Qiao" :
Hi,
As described in this issue, a new result set format is wanted by users. I'd
