Hi
Can you please provide more details on the issue
1. Steps to reproduce the issue
2. Which Carbondata version you are using
Regards
Manish Gupta
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
Hi Yixu2001,
Can u please provide the detailed step to reproduce this issue.
-Regards
Kumar Vishal
On Thu, Apr 12, 2018 at 9:16 PM, yixu2001 wrote:
> dev
>
> version spark2.1.1 carbondata 1.3.1
>
>
> yixu2001
>
> From: yixu2001
> Date: 2018-04-12 14:17
> To: dev
>
Hi Yaojinguo,
The issue is we currently load all the index info into driver memory
which causes a large memory footprint irrespective of query type(filter or
full scan).
This can be avoided by loading only required segment's index information
for filter queries.
We could achieve it by
I think the problem may be metadata related. What's your thrift version? Have
you update carbon version recently after the data is loaded? FROM MOBILE EMAIL
CLIENT On 04/16/2018 15:51, Liang Chen wrote: Hi From the log message, seems
like can't find the data files. Can you provide more detail
Hi
>From the log message, seems like can't find the data files.
Can you provide more detail info :
1. How you created carbonsession and how loaded data.
2. Have you deployed cluster or only single machine?
Regards
Liang
喜之郎 wrote
> hi all, when I use carbondata to run a query "select count(*)