Github user zuyu commented on the issue:
https://github.com/apache/incubator-quickstep/pull/122
@jianqiao Many query-optimizer-distributed-execution-generator unit tests
failed due to missing LIP data structure `LIPFilterBuilder` in `QueryContext`
in the distributed case.
```
33 -
quickstep_queryoptimizer_tests_distributed_executiongenerator_delete
(OTHER_FAULT)
34 -
quickstep_queryoptimizer_tests_distributed_executiongenerator_distinct
(OTHER_FAULT)
37 -
quickstep_queryoptimizer_tests_distributed_executiongenerator_insert
(OTHER_FAULT)
38 -
quickstep_queryoptimizer_tests_distributed_executiongenerator_join (OTHER_FAULT)
39 -
quickstep_queryoptimizer_tests_distributed_executiongenerator_select
(OTHER_FAULT)
40 -
quickstep_queryoptimizer_tests_distributed_executiongenerator_stringpatternmatching
(OTHER_FAULT)
41 -
quickstep_queryoptimizer_tests_distributed_executiongenerator_tablegenerator
(OTHER_FAULT)
42 -
quickstep_queryoptimizer_tests_distributed_executiongenerator_update
(OTHER_FAULT)
$ ctest -VV -R
quickstep_queryoptimizer_tests_distributed_executiongenerator_delete
34: [ RUN ]
DISTRIBUTED_EXECUTION_GENERATOR_TEST/TextBasedTest.CompareOutputs/0
34: F1030 22:46:20.846637 1064960 QueryContext.hpp:331] Check failed:
static_cast<std::size_t>(id) < lip_deployments_.size() (0 vs. 0)
```
To me, like other data members in `QueryContext`, if possible,
`LIPFilterBuilder` would be serialized into `QueryContext proto`, and then
deserialized at the beginning of the query execution, instead of the current
way that creates during constructing a `WorkOrder`.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
