Re: Contribution to Calcite
Hello Nikolay, I have added you as a Calcite contributor. Best regards, Ruben On Thu, Jan 19, 2023 at 1:41 PM Николай Ижиков wrote: > Hello, Calcite. > > My name is Nikolay Izhikov. > Please, add me to the Calcite contributors so I can assign tickets to > myself and resolve them. > > My jira id - nizhikov
Contribution to Calcite
Hello, Calcite. My name is Nikolay Izhikov. Please, add me to the Calcite contributors so I can assign tickets to myself and resolve them. My jira id - nizhikov
Re: do some code contribution on calcite
I have added you as a contributor. Welcome to Calcite! -- Michael Mior mm...@apache.org Le mar. 28 sept. 2021 à 16:17, zxyoung a écrit : > > I want to fix some bug in calcite jira and assign some issue to myself. > My jira username is xuyangzhong. > Can anyone help me? > Thanks very much :)
do some code contribution on calcite
I want to fix some bug in calcite jira and assign some issue to myself. My jira username is xuyangzhong. Can anyone help me? Thanks very much :)
Re: [contribution request] calcite contribution.
Hey Hanu, I've added you as a contributor in JIRA. Francis On 3/03/2020 9:13 am, hanu mapr wrote: Hi All, I would like to contribute to calcite. Can you please provide me the required contribution permissions to assign a bug to my JIRA account? JIRA account ID: hanu.ncr Thanks, -Hanu
[contribution request] calcite contribution.
Hi All, I would like to contribute to calcite. Can you please provide me the required contribution permissions to assign a bug to my JIRA account? JIRA account ID: hanu.ncr Thanks, -Hanu
Re: Contribution to calcite elastic search development
Note that in the interim, you can define a view on top of the raw schema that will let you expand columns from the _MAP column into tables which are more convient to query. -- Michael Mior mm...@apache.org Le lun. 18 févr. 2019 à 12:21, Andrei Sereda a écrit : > > Hi Kumar, > > Currently elastic table row type is "Map". I'm working on > converting elastic mapping directly to RelDataType [1]. > When done, you'll be able to query document attributes directly (as in > `select address from user` instead of `select _MAP['address'] from user`) > (discussion here [2]) > > Regarding missing features in elastic adapter, we can discuss them here and > create JIRAs individually. Please let me know what functionalities you need. > > If you would like to contribute to Calcite a good place to start is jira > issues (https://issues.apache.org/jira/projects/CALCITE). Read tutorial ( > https://calcite.apache.org/docs/tutorial.html) first and study CSV adapter > code. > > Thanks, > Andrei. > > [1] > https://calcite.apache.org/apidocs/org/apache/calcite/rel/type/RelDataType.html > > [2] > https://lists.apache.org/thread.html/4fdb9fb396730168704f6bd9d3b57a7baa5b41241f26db7c0cc84729@%3Cdev.calcite.apache.org%3E33[3] > aa > > On Mon, Feb 18, 2019 at 6:15 AM Shashwat Kumar > wrote: > > > Hi all, > > > > I find that calcite for elasticsearch is still at very early stage and does > > not support even select queries seamlessly. For example, > > *SELECT id, address FROM *user needs to be done as *SELECT _MAP['id'], > > _MAP['address'] FROM 'user'* > > > > I am using calcite elasticsearch in my project and would like to contribute > > in it. I would like to know if there is any priority list of items which I > > can take or other ongoing developments in it. > > Kindly guide me through other necessary resources or guidelines. > > > > -- > > Regards > > Shashwat Kumar > >
Re: Contribution to calcite elastic search development
Hi Kumar, Currently elastic table row type is "Map". I'm working on converting elastic mapping directly to RelDataType [1]. When done, you'll be able to query document attributes directly (as in `select address from user` instead of `select _MAP['address'] from user`) (discussion here [2]) Regarding missing features in elastic adapter, we can discuss them here and create JIRAs individually. Please let me know what functionalities you need. If you would like to contribute to Calcite a good place to start is jira issues (https://issues.apache.org/jira/projects/CALCITE). Read tutorial ( https://calcite.apache.org/docs/tutorial.html) first and study CSV adapter code. Thanks, Andrei. [1] https://calcite.apache.org/apidocs/org/apache/calcite/rel/type/RelDataType.html [2] https://lists.apache.org/thread.html/4fdb9fb396730168704f6bd9d3b57a7baa5b41241f26db7c0cc84729@%3Cdev.calcite.apache.org%3E33[3] aa On Mon, Feb 18, 2019 at 6:15 AM Shashwat Kumar wrote: > Hi all, > > I find that calcite for elasticsearch is still at very early stage and does > not support even select queries seamlessly. For example, > *SELECT id, address FROM *user needs to be done as *SELECT _MAP['id'], > _MAP['address'] FROM 'user'* > > I am using calcite elasticsearch in my project and would like to contribute > in it. I would like to know if there is any priority list of items which I > can take or other ongoing developments in it. > Kindly guide me through other necessary resources or guidelines. > > -- > Regards > Shashwat Kumar >
Contribution to calcite elastic search development
Hi all, I find that calcite for elasticsearch is still at very early stage and does not support even select queries seamlessly. For example, *SELECT id, address FROM *user needs to be done as *SELECT _MAP['id'], _MAP['address'] FROM 'user'* I am using calcite elasticsearch in my project and would like to contribute in it. I would like to know if there is any priority list of items which I can take or other ongoing developments in it. Kindly guide me through other necessary resources or guidelines. -- Regards Shashwat Kumar
