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

Hope fuzzy query could support multi-device #3945

Closed
LIU-WEI-git opened this issue Sep 11, 2021 · 4 comments
Closed

Hope fuzzy query could support multi-device #3945

LIU-WEI-git opened this issue Sep 11, 2021 · 4 comments

Comments

@LIU-WEI-git
Copy link
Contributor

LIU-WEI-git commented Sep 11, 2021

I find the fuzzy query of IoTDB doesn't support multi device. Hope it can be supported in the future.

In my scenario, I store the value of the index as LayerName to index some fields. For example, there is a table called service_traffic. It has 4 fields: id, type, group, name. I make the value of id, type and name as part of the storage path to achieve the effect of index. Eventually the data from the same table is spread across multiple devices.

When I used like clause to fuzzy query, I got a Exception: Msg: 500: [INTERNAL_SERVER_ERROR] Exception occurred while executing "select * from root.skywalking.service_traffic.*."0".* where name like '%1%'". class org.apache.iotdb.db.qp.logical.crud.LikeOperator cannot be cast to class org.apache.iotdb.db.qp.logical.crud.BasicFunctionOperator (org.apache.iotdb.db.qp.logical.crud.LikeOperator and org.apache.iotdb.db.qp.logical.crud.BasicFunctionOperator are in unnamed module of loader 'app')

In debug mode, I found the Exception occurred on ConcatPathOptimizer. The LikeOperator cannot be cast to BasicFunctionOperator.

image

OS: Win10, Version: 0.12.2

@HTHou
Copy link
Contributor

HTHou commented Sep 11, 2021

@ijihang Any idea about this issue?

@ijihang
Copy link
Contributor

ijihang commented Sep 13, 2021

Ok,I'll implement this function right away

@HTHou
Copy link
Contributor

HTHou commented Sep 14, 2021

@LIU-WEI-git The latest rel/0.12 branch fixed this issue. You can try it now.

@LIU-WEI-git
Copy link
Contributor Author

wow~, thanks a lot. : )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants