Add some neccessary tables and schemas and accomplish the function that use a JSON to contain the physical plan.
The above picture is the sample output for the query "select l_orderkey, l_partkey, l_superkey from testORC where l_tax = 122 AND (l_quantity < 100 AND l_quantity > 50)". Because by testing some sample queries, I found that for operators "AND" and "OR", the number of corresponding operands
may be larger than 2. And thus I use "operand 1", "operand 2" "operand 3" and so on to denote them in the JSON file, rather than "left" and "right".
To run the sample program, use make HuskyORCQueryPlan
Add some neccessary tables and schemas and accomplish the function that use a JSON to contain the physical plan.
The above picture is the sample output for the query "select l_orderkey, l_partkey, l_superkey from testORC where l_tax = 122 AND (l_quantity < 100 AND l_quantity > 50)". Because by testing some sample queries, I found that for operators "AND" and "OR", the number of corresponding operands may be larger than 2. And thus I use "operand 1", "operand 2" "operand 3" and so on to denote them in the JSON file, rather than "left" and "right".
To run the sample program, use make HuskyORCQueryPlan