Re: Upgraded to 3.0.17, stop here or move forward?

2018-10-10 Thread Anup Shirolkar
Hi Ricardo, Yes no harm in executing upgradesstables multiple times. Regarding the aggregate functions, you mentioned the data is pre-aggregated in buckets. Does that mean the records which are to be used in aggregate function are part of a single partition. In my opinion, query performance is

Re: Upgraded to 3.0.17, stop here or move forward?

2018-10-10 Thread Riccardo Ferrari
Thank you Anup, Yup, the upgradesstables is a step I generally take before (to make sure I'm on the latest version) and after to make sure I'm updating to the latest sstable version supported by the version. I know it's redundant and not necessary but I read it does not hurt. I am looking into

Re: Upgraded to 3.0.17, stop here or move forward?

2018-10-09 Thread Anup Shirolkar
Hi, Yes it makes sense to move to 3.11.3 The release has features and bug fixes which should be useful to your cluster. However, if you are planning to use GROUP_BY, UDFs etc. Please be cautious about the performance implications it may cause if not done with suitable queries. I am not aware

Upgraded to 3.0.17, stop here or move forward?

2018-10-09 Thread Riccardo Ferrari
Hi list, We recently upgraded our small cluster to the latest 3.0.17. Everything was nice and smooth, however I am wondering if ti make sense to keep moving forward and upgarde to the latest 3.11.3? We really need something like the GROUP_BY and UFF/UDA seems limited wrt our use-case. Does it