Re: [VOTE] Apache CarbonData 2.1.1(RC1) release
-1 as pending major fixes. Regards, Ramana On Thu, 18 Mar, 2021, 20:37 Kunal Kapoor, wrote: > -1, lets wait for the pending jira's to get resolved > > On Thu, 18 Mar 2021, 7:30 pm Kumar Vishal, > wrote: > > > -1 > > -Regards > > Kumar Vishal > > > > On Thu, 18 Mar 2021 at 6:35 PM, David CaiQiang > > wrote: > > > > > -1, please fix the pending defect and merge the completed PR at first. > > > > > > > > > > > > - > > > Best Regards > > > David Cai > > > -- > > > Sent from: > > > > http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/ > > > > > >
[DISCUSSION] Describe complex columns
Hi, Currently describe formatted displays the column information of a table and some additional information. When complex types such as ARRAY, STRUCT, and MAP types are present in table, column definition can be long and it’s difficult to read in a nested format. For complex types available, the DESCRIBE output can be formatted to avoid long lines for multiple fields. We can pass the complex field name to the command and visualize its structure as if were a table. DDL Commands: DESCRIBE fieldname ON [db_name.]table_name; DESCRIBE short [db_name.]table_name; Please let me know your valid inputs about the same. Following is the link to the design document. https://docs.google.com/document/d/1uNCByKR09Up9S2hpiEXYDA8XXIEZ2jI9PMSzMIVJ0Js/edit Thanks, Shreelekhya -- Sent from: http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
[DISCUSSION] Support alter schema for complex types
Hi everyone, Currently carbon only supports altering schema for primitive types. We can extend it to complex columns too - 1) alter add complex column(array/struct) 2) alter drop complex column(array/struct) 3) alter change datatype/rename complex column(array/struct) Here phase-1 focuses only on non-nested complex columns. Phase-2 will later target nested ones. Please let me know your valid inputs about the same. Following is the link to the design document. https://docs.google.com/document/d/1DhhkVXM8rMvOuKDZeccJpFEfO3VkA9C0c7JHCV88NXI/edit Thanks, Akshay -- Sent from: http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
Re: DISCUSSION: propose to activate "Issues" of https://github.com/apache/carbondata
Then i don't think moving to github issues would be good. JIRA is much better suited for our needs On Thu, Mar 18, 2021 at 8:48 PM Jean-Baptiste Onofre wrote: > Hi, > > I don’t think so. GH Issues is not as "advanced" as Jira. > > Regards > JB > > > Le 18 mars 2021 à 16:17, Kunal Kapoor a > écrit : > > > > Hi, > > Is there a way to create story and subtask in github issues similar to > jira? > > > > > > On Thu, 18 Mar 2021, 6:12 pm Jean-Baptiste Onofre, > wrote: > > > >> Hi, > >> > >> First of all, I full agree with Liang. > >> > >> I think it makes sense to keep the workflow: > >> > >> - issue > >> - PullRequest > >> - checks (CI) > >> - merge > >> > >> I think that we can already use Github issue (and even Github actions if > >> we want). > >> > >> Regards > >> JB > >> > >>> Le 18 mars 2021 à 12:59, Liang Chen a écrit > : > >>> > >>> Hi > >>> > >>> As you know, for better managing community, i propose to put "Issues, > >> Pull > >>> Request, Code" together and request Apache INFRA to activate "Issues" > of > >>> github. > >>> > >>> Open discussion, please input your comments. > >>> > >>> Regards > >>> Liang > >> > >> > >
Re: DISCUSSION: propose to activate "Issues" of https://github.com/apache/carbondata
Hi, I don’t think so. GH Issues is not as "advanced" as Jira. Regards JB > Le 18 mars 2021 à 16:17, Kunal Kapoor a écrit : > > Hi, > Is there a way to create story and subtask in github issues similar to jira? > > > On Thu, 18 Mar 2021, 6:12 pm Jean-Baptiste Onofre, wrote: > >> Hi, >> >> First of all, I full agree with Liang. >> >> I think it makes sense to keep the workflow: >> >> - issue >> - PullRequest >> - checks (CI) >> - merge >> >> I think that we can already use Github issue (and even Github actions if >> we want). >> >> Regards >> JB >> >>> Le 18 mars 2021 à 12:59, Liang Chen a écrit : >>> >>> Hi >>> >>> As you know, for better managing community, i propose to put "Issues, >> Pull >>> Request, Code" together and request Apache INFRA to activate "Issues" of >>> github. >>> >>> Open discussion, please input your comments. >>> >>> Regards >>> Liang >> >>
Re: DISCUSSION: propose to activate "Issues" of https://github.com/apache/carbondata
Hi, Is there a way to create story and subtask in github issues similar to jira? On Thu, 18 Mar 2021, 6:12 pm Jean-Baptiste Onofre, wrote: > Hi, > > First of all, I full agree with Liang. > > I think it makes sense to keep the workflow: > > - issue > - PullRequest > - checks (CI) > - merge > > I think that we can already use Github issue (and even Github actions if > we want). > > Regards > JB > > > Le 18 mars 2021 à 12:59, Liang Chen a écrit : > > > > Hi > > > > As you know, for better managing community, i propose to put "Issues, > Pull > > Request, Code" together and request Apache INFRA to activate "Issues" of > > github. > > > > Open discussion, please input your comments. > > > > Regards > > Liang > >
Re: [VOTE] Apache CarbonData 2.1.1(RC1) release
-1, lets wait for the pending jira's to get resolved On Thu, 18 Mar 2021, 7:30 pm Kumar Vishal, wrote: > -1 > -Regards > Kumar Vishal > > On Thu, 18 Mar 2021 at 6:35 PM, David CaiQiang > wrote: > > > -1, please fix the pending defect and merge the completed PR at first. > > > > > > > > - > > Best Regards > > David Cai > > -- > > Sent from: > > http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/ > > >
Re: [VOTE] Apache CarbonData 2.1.1(RC1) release
-1 -Regards Kumar Vishal On Thu, 18 Mar 2021 at 6:35 PM, David CaiQiang wrote: > -1, please fix the pending defect and merge the completed PR at first. > > > > - > Best Regards > David Cai > -- > Sent from: > http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/ >
Re: Apply to open 'Issues' tab in Apache CarbonData github
Yes, we just have to request infra to enable GitHub issues. I’m already using GitHub Actions on some projects, so it should not be a problem for GitHub issues. Regards JB > Le 30 déc. 2019 à 09:53, Kunal Kapoor a écrit : > > Hi, > +1 for Ajantha's suggestion. > > The use of issues tab is not clear from this post. Please give details on > how you are planning to use it. > > Thanks > Kunal Kapoor > > > On Mon, Dec 30, 2019 at 2:03 PM Akash Nilugal > wrote: > >> Hi, >> >> +1 for ajantha's suggestion. >> >> Many Open source communities use slack for any discussion, it has got good >> interface UI and it even supports chat. It will be helpful for any new >> developer who is interested in carbondata. >> Currently many people cannot follow mail chain. >> >> Regards, >> Akash R Nilugal >> >> On 2019/12/24 05:33:22, Ajantha Bhat wrote: >>> If planning to issues tab just to replace mailing list problems. I would >>> suggest we can start using "*slack*". >>> >>> Many companies and open source communities uses slack (I have used from >>> presto sql community). It supports thread based conversations and >> searching >>> is easy. It also provides option to create multiple channels and it works >>> in china without any vpn. >>> >>> Please have a look at it once. >>> >>> Thanks, >>> Ajantha >>> >>> On Mon, 23 Dec, 2019, 11:31 pm 恩爸, <441586...@qq.com> wrote: >>> Hi Liang: Carbondata users can raise issues in github's issues to ask any questions, the function is the same as mailing list, many chinese users can't access mailing list and are used to use github's issues. To track and record real issues, it still needs to use Apache JIRA. -- Original -- From: "Liang Chen [via Apache CarbonData Dev Mailing List archive]"< ml+s1130556n88594...@n5.nabble.com>; Date: Sun, Dec 22, 2019 09:14 PM To: "恩爸"<441586...@qq.com>; Subject: Re: Apply to open 'Issues' tab in Apache CarbonData github Hi +1 from my side. One question : what issues should be raised to Apache JIRA? what issues will be raised to github's issue ? It is better to give the clear definition. Regards Liang xm_zzc wrote > Hi community: > I suggest community to open 'Issues' tab in carbondata github page, we > can use this feature to collect the information of carbondata users, like > this: https://github.com/apache/incubator-shardingsphere/issues/234 , > users can add company information which uses carbondata on it willingly > and we can add these info in Carbondata website. > what do you think about this? -- Sent from: >> http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/ If you reply to this email, your message will >> be added to the discussion below: >> http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/Apply-to-open-Issues-tab-in-Apache-CarbonData-github-tp88436p88594.html To start a new topic under Apache CarbonData >> Dev Mailing List archive, email ml+s1130556n1...@n5.nabble.com To unsubscribe from Apply to open 'Issues' tab in >> Apache CarbonData github, click here. NAML >>> >>
Re: [VOTE] Apache CarbonData 2.1.1(RC1) release
-1, please fix the pending defect and merge the completed PR at first. - Best Regards David Cai -- Sent from: http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
Re: Apply to open 'Issues' tab in Apache CarbonData github
I will apply Issues table via INFRA Regards Liang -- Sent from: http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
Re: [VOTE] Apache CarbonData 2.1.1(RC1) release
-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/
Re: DISCUSSION: propose to activate "Issues" of https://github.com/apache/carbondata
Hi The github issues tab will replace JIRA. Regards Liang Ajantha Bhat wrote > Hi, > > After opening github issues tab, are we going to stop using JIRA? > If we keep both, then when to use JIRA and when to use issues? > > Also as we have slack channel now, if user face issues then can directly > discuss in slack for quick support. > > Thanks, > Ajantha > > On Thu, 18 Mar, 2021, 5:29 pm Liang Chen, > chenliang613@ > wrote: > >> Hi >> >> As you know, for better managing community, i propose to put "Issues, >> Pull >> Request, Code" together and request Apache INFRA to activate "Issues" of >> github. >> >> Open discussion, please input your comments. >> >> Regards >> Liang >> -- Sent from: http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
Re: DISCUSSION: propose to activate "Issues" of https://github.com/apache/carbondata
Hi, First of all, I full agree with Liang. I think it makes sense to keep the workflow: - issue - PullRequest - checks (CI) - merge I think that we can already use Github issue (and even Github actions if we want). Regards JB > Le 18 mars 2021 à 12:59, Liang Chen a écrit : > > Hi > > As you know, for better managing community, i propose to put "Issues, Pull > Request, Code" together and request Apache INFRA to activate "Issues" of > github. > > Open discussion, please input your comments. > > Regards > Liang
Re: DISCUSSION: propose to activate "Issues" of https://github.com/apache/carbondata
Hi, After opening github issues tab, are we going to stop using JIRA? If we keep both, then when to use JIRA and when to use issues? Also as we have slack channel now, if user face issues then can directly discuss in slack for quick support. Thanks, Ajantha On Thu, 18 Mar, 2021, 5:29 pm Liang Chen, wrote: > Hi > > As you know, for better managing community, i propose to put "Issues, Pull > Request, Code" together and request Apache INFRA to activate "Issues" of > github. > > Open discussion, please input your comments. > > Regards > Liang >
DISCUSSION: propose to activate "Issues" of https://github.com/apache/carbondata
Hi As you know, for better managing community, i propose to put "Issues, Pull Request, Code" together and request Apache INFRA to activate "Issues" of github. Open discussion, please input your comments. Regards Liang
Re: [VOTE] Apache CarbonData 2.1.1(RC1) release
-1, need to fix some major defects Regards Liang -- Sent from: http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
