+1 for complete removal.
On Wed, Nov 29, 2017 at 1:45 PM, ShaoFeng Shi
wrote:
> Billy, I don't see a need for "advanced user could enable it also." Do
> you have such a case?
>
> For the legacy cube, it can continue to build, the backend code won't be
> removed during
Billy, I don't see a need for "advanced user could enable it also." Do you
have such a case?
For the legacy cube, it can continue to build, the backend code won't be
removed during this phase.
2017-11-28 22:58 GMT+08:00 Billy Liu :
> +1 to turn this feature off by default.
+1 to turn this feature off by default. The advanced user could enable it
also.
2017-11-27 13:53 GMT+08:00 Luke Han :
> +1 to remove it from new release, people could backport to new version
> with previous code
>
>
> Best Regards!
> -
>
> Luke Han
>
> On
+1 to remove it from new release, people could backport to new version with
previous code
Best Regards!
-
Luke Han
On Sun, Nov 26, 2017 at 9:40 PM, ShaoFeng Shi
wrote:
> Last year I raised this discussion but didn't have follow-up action.
>
> Now
Last year I raised this discussion but didn't have follow-up action.
Now we see there are still some new users misuse this feature, and then
face performance and maintenance issues.
In Kylin 2.1, the new "query pushdown" feature can forward the Cube
unmatched queries to alternative query engines