+1
Regards,
Indhumathi M
On Tue, 21 Nov 2023 at 1:07 AM, Liang Chen wrote:
> Hi
>
>
>
> I submit the Apache CarbonData 2.3.1 (RC1) to your vote.
>
> 1. Key features of this release are highlighted as below..
>
> - Fixed performance
, Flink, Presto etc. to
leverage new features.
Regards,
Indhumathi M
On Thu, Oct 19, 2023 at 1:28 PM Liang Chen wrote:
> As you know, Carbondata as datastore and dataformat already be quite good
> and mature.
> I want to create the thread via mailing list to open discuss what are t
+1. I would also like to add Brijoo as a new PMC member, since his
contributions for the project looks great.
Regards,
Indhumathi M
On Fri, 5 Aug 2022 at 3:33 PM, Jacky Li wrote:
>
> Hi community,
>
> In order to help further growing Apache CarbonData community, I would
>
Hello Shreelekhya,
Please find the comments inline in the design document link shared.
Regards,
Indhumathi M
On 2022/03/17 16:09:10 Shreelekhya Gampa wrote:
> Hi everyone,
>
> Currently, MV in carbon is supported as incremental or full refresh load
> based on the type of query.
Congratulations Vikram !!
Regards,
Indhumathi M
On Sat, 12 Feb 2022 at 9:19 AM, Liang Chen wrote:
> We are pleased to announce that the PMC has invited Vikram Ahuja as new
>
> Apache CarbonData committer, and the invite has been accepted!
>
>
> Congrats to Vikram Ahuja
+1
Regards,
Indhumathi M
On Wed, 19 Jan 2022 at 9:27 PM, Kunal Kapoor
wrote:
> Hi All,
> I submit the Apache CarbonData 2.3.0(RC2) for your vote.
>
>
> *1.Release Notes:*
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12349262=Html=12320220=Create
log4j known to be affected by the vulnerability.
We have reviewed the code and
run the vulnerability tool, as per the tool report, these three
vulnerabilities (CVE-2021-44228,
CVE-2021-45046,CVE-2021-45105) are not identified.
Regards,
Indhumathi M
-1, Agree with Liang Chen to include PR's : 4240,4241,4242,4243 in release
Regards,
Indhumathi M
On Mon, Dec 20, 2021 at 7:09 PM Kunal Kapoor
wrote:
> Hi All,
>
> I submit the Apache CarbonData 2.3.0(RC1) for your vote.
>
>
> *1.Release Notes:*
>
> https://issue
+1 for this feature. we can keep the same behavior as in Spark
Regards,
Indhumathi M
On 2021/10/10 19:47:31, Mahesh Raju Somalaraju
wrote:
> Dear Community,
>
> This mail is regarding char/varchar implementation in carbondata. Recently
> Spark3.1 is added char/varchar implem
ingest ?
Regards,
Indhumathi M
On Tue, 31 Aug 2021 at 11:18 PM, Akash Nilugal
wrote:
> Hi Community,
>
> OLTP systems like Mysql are used heavily for storing transactional data in
> real-time and the same data is later used for doing fraud detection and
> taking various data-driven bus
+1
Regards,
Indhumathi M
On Mon, Aug 2, 2021 at 12:33 PM Akash Nilugal
wrote:
> Hi All,
>
> I submit the Apache CarbonData 2.2.0(RC2) for your vote.
>
>
> *1.Release Notes:*
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12347869=Html=12320220=Cre
-1
Let us wait for some more PR’s (4148, 4164,4157) to be merged
Regards,
Indhumathi
On Tue, 6 Jul 2021 at 12:45 PM, Akash Nilugal
wrote:
> Hi All,
>
> I submit the *Apache CarbonData 2.2.0(RC1) *for your vote.
>
>
>
> *1. Release Notes:*
>
> https://is
from N*M times to M times.
I have attached new design document in the JIRA.
CARBONDATA-4166 <https://issues.apache.org/jira/browse/CARBONDATA-4166>
Regards,
Indhumathi
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
Hello all,
Please find the design document link attached in JIRA, CARBONDATA-4166
<https://issues.apache.org/jira/browse/CARBONDATA-4166>
Any inputs/suggestions from the community is most welcomed.
Regards,
Indhumathi
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1
Congratulations Akash
Regards,
Indhumathi
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
on() | x |
-+-+--
To achieve this, a solution could be to, run query with IN_POLYGON
udf of each polygon and finally make a union of query result.
Will update design on further analysis.
Any opinion or suggestions are welcomed.
Thanks,
Indhumathi M
--
Sent from:
http:
+1
Regards,
Indhumathi M
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
+1 for design.
Please find my comments.
1. About updating IndexStatus.ENABLED property, Need to consider
compatibility scenarios as well.
2. Can update the query behavior when carbon.enable.distributed.index
and carbon.disable.index.server.fallback is enabled.
Regards,
Indhumathi M
+1
Regards
Indhumathi M
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
, please update design for those DDL commands.
Regards,
Indhumathi M
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
+1. Please update design, for Map type having more than one level of complex
types.
For example, map>
Regards,
Indhumathi M
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
, where polygon data exists in a table.
Please find below link of design doc. Please check and give
your inputs/suggestions.
https://docs.google.com/document/d/11PnotaAiEJQK_QvKsHznDy1I9tO4idflW32LstwcLhc/edit#heading=h.yh6qp815dh3p
Thanks & Regards,
Indhumathi M
--
Sent from:
http://ap
-1, some open PR's related to SI, MV and others are also need to be taken
Regards,
Indhumathi M
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
+1, Agree with kunal, to show segment ID for current load.
Regards,
Indhumathi M
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
and SI table Sync during register index?
Please let me know your solutions about the same.
Regards,
Indhumathi M
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
Hi Nihal,
I also feel, it is good to display only the segment Id at the end of
command, similar to
Update Command, which returns number of updated rows. No need to add other
details (It can
be enhanced in Show segments command if needed).
Regards,
Indhumathi M
On Mon, Jan 18, 2021 at 9:54 AM
+1
Regards.
Indhumathi
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
Thank you all
Regards
Indhumathi
On Wed, Oct 7, 2020 at 8:21 PM Ravindra Pesala
wrote:
> Congrats Indumathi !
>
>
> On Wed, 7 Oct 2020 at 10:29 AM, manish gupta
> wrote:
>
> > Congratulations Indumathi
> >
> > Regards
> > Manish Gupta
> >
&
with expressions like AND, cannot be supported on SI, since the array data
will
flattened in SI.
Inputs and suggestions for any new solution/ changes in above solution are
most welcomed.
Regards,
Indhumathi
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
+ 1
I have a question.
For each update and delete operation, carbon will create a delta file to
keep deleted row ids. For sequential update and delete operation using
CarbonSDK, will these delta files will be compacted to single delta file
using horizontal compaction?
Regards,
Indhumathi
Congratulations Kunal!
Regards,
Indhumathi
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
1. can you tell me how you gonna read the in max? I mean to say, are you
going to store the segment level min max for all the column or since you
said blocklevel, it means for every carbondata file
you are going to store it? If it is block level,in case of more file,
segment file size might
under
different databases.
Datamaps will be saved to database folder specified while creating datamap.
Any suggestions/inputs from the community is appreciated.
Thanks
Indhumathi
part we will make
it inline to datamap interface.
So design document is attached in JIRA, please give your suggestion/inputs.
JIRA Link: CARBONDATA-3680
<https://issues.apache.org/jira/browse/CARBONDATA-3680>
Thanks & Regards,
Indhumathi M
data will be encoded and stored in segment file.
Any suggestions/inputs from the community is appreciated.
Thanks
Indhumathi
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
index also support
Aggregation queries on
geographical location data?
Thanks & Regards,
Indhumathi
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
Hello all,
Please find the updated design document for Incremental dataloading
at the below link.
https://docs.google.com/document/d/1AACOYmBpwwNdHjJLOub0utSc6JCBMZn8VL5CvZ9hygA/edit?usp=sharing
On Thu, Apr 4, 2019 at 12:29 PM chetdb wrote:
> 1. Will dataloading to MV be supported for all the
Hi qiuchenjian,
*1) lazy or non-lazy mode when using different option *
Currently MV supports data load through only lazy mode. Incremental data
loading
will be supported for the same
*2)reuse the existing MV data and generate new segment like you describe or
overwrite MV table directly
. What are the Authentication properties that has to be configured to
store carbondata files on to OBSFS location?
Hope all these points will be covered in design document.
Regards,
Indhumathi M
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
d generate a
Carbon Row.
Please feel free to provide your comments and suggestions.
Regards,
Indhumathi M
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
Hi Jacky Li,
Yes. I am extending PR-2670 and working on that, for binary data type.
Regards,
Indhumathi M
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
d decode it to a newBinaryPage().
4. For Querying Binary data type columns, implement a BinaryVectorFiller,
which fills byte array data to CarbonColumnVector.
Please provide your inputs and comments. Any suggestion from community is
most welcomed.
Regards,
Indhumathi
--
Sent from:
http:
Hi all,
Please check the jira for the design document.
**jira link:**
https://docs.google.com/document/d/1Jne8vNZ3OSYmJ_72hTIk_5I4EeIVtxGNE5mN_hBlnVE/edit?usp=sharing
<https://docs.google.com/document/d/1Jne8vNZ3OSYmJ_72hTIk_5I4EeIVtxGNE5mN_hBlnVE/edit?usp=sharing>
Regards,
Indhum
and comments. Any suggestion from community is
most
welcomed.
Regards,
Indhumathi
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
and suggestions. I am working on
the design document and will upload soon.
**Jira Link:**
https://issues.apache.org/jira/browse/CARBONDATA-2876
<https://issues.apache.org/jira/browse/CARBONDATA-2876>
Regards
Indhumathi M
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130
Hi Sujith,
Thanks for your review. Please find my comments inline.
a)Can we use map data type columns as partition key columns?
** No. It has been already mentioned in Impacted Feature Analysis. **
b) It will be clear if you can mention all the data types which is
supported, like do we support
ile/t341/MAP_DATA-TYPE_SUPPORT.pdf>
Please find the link for design document.
https://docs.google.com/document/d/1HHe2fdkIh3Jyz1y3494_2kGRSc4muTWuilAmwg5lpVw/edit?usp=sharing
<https://docs.google.com/document/d/1HHe2fdkIh3Jyz1y3494_2kGRSc4muTWuilAmwg5lpVw/edit?usp=sharing>
Regards
47 matches
Mail list logo