Hi Lu Cao,
In my previous experience on “cube” engine, no matter it is ROLAP or MOLAP, it
is something above SQL layer, because it not only need user to establish cube
schema by transform metadata from datawarehouse star schema but also the engine
defines its own query language like MDX, and
+1
2017-10-15 21:19 GMT+08:00 Lu Cao :
> Sure, will create the Jira ticket.
>
> Thanks,
> Lionel
>
> On Sun, Oct 15, 2017 at 2:29 PM, Liang Chen
> wrote:
>
> > Hi lionel
> >
> > As per mailing list discussion result, no objection. so can you create
Hi Jacky,
If user want to create a cube on main table, does he/she have to create
multiple pre-aggregate tables? It will be a heavy workload to write so many
CTAS commands. If user only need create a few pre-agg tables, current
carbon already can support this requirement, user can create table
Hi Liang,
For alter table, data update/delete, and delete segment, they are the same.
So I write in document “ User can manually perform this operation and rebuild
pre-aggregate table as
update scenario”
User need to drop the associated aggregate table and perform alter table, or
data
Hi Jacky
Thanks for you started this discussion, this is a great feature in
carbondata.
One question:
For sub_jar "Handle alter table scenarios for aggregation table", please
give more detail info.
Just i viewed the pdf attachment as below, looks no need to do any handles
for agg table if users
Hi lionel
As per mailing list discussion result, no objection. so can you create an
umbrella jira to remove spark 1.5 & 1.6 code in 1.3.0.
Regards
Liang
lionel061201 wrote
> Hi community,
> Currently we have three spark related module in carbondata(spark 1.5, 1.6,
> 2.1), the project has