You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, all the label data in OpenDigger is stored directly in git repo under the labeled_data folder. And for queries with labels involved, we construct the query SQL in text mode and pass into the SQL directly. But with more and more labels come into OpenDigger, this may lead to multiple problems like the SQL text will be quite long or even exceed the requirement.
For future use, I would like to refactor the label module and store all the label data structure into ClickHouse table and then we can use SQL with label table to inject label filter functions.
But this also requires the ClickHouse version to be 22.4+ to support recursive CTEs since the label system supports multi-layer with sub labels. So just open this issue for recording now.
The text was updated successfully, but these errors were encountered:
Description
Right now, all the label data in OpenDigger is stored directly in git repo under the
labeled_data
folder. And for queries with labels involved, we construct the query SQL in text mode and pass into the SQL directly. But with more and more labels come into OpenDigger, this may lead to multiple problems like the SQL text will be quite long or even exceed the requirement.For future use, I would like to refactor the label module and store all the label data structure into ClickHouse table and then we can use SQL with label table to inject label filter functions.
But this also requires the ClickHouse version to be 22.4+ to support recursive CTEs since the label system supports multi-layer with sub labels. So just open this issue for recording now.
The text was updated successfully, but these errors were encountered: