I would advocate using JIRA. For this purpose, I have logged 
https://issues.apache.org/jira/browse/CALCITE-2031 
<https://issues.apache.org/jira/browse/CALCITE-2031>. 

The list of not-yet-implemented functions is in 
https://github.com/apache/calcite/blob/master/core/src/test/resources/sql/spatial.iq
 
<https://github.com/apache/calcite/blob/master/core/src/test/resources/sql/spatial.iq>
 - search for “# Not implemented”.

If you are working on a function or functions, add a comment to the JIRA case 
so that no one else starts working on the same thing.

Julian


> On Nov 2, 2017, at 6:45 AM, Michael Mior <[email protected]> wrote:
> 
> Any reason this can't just be done as a JIRA issue? You could also connect
> this with a pull request that includes proposed documentation for
> interfaces that you think should be implemented.
> 
> --
> Michael Mior
> [email protected]
> 
> 2017-11-01 20:49 GMT-04:00 Edmon Begoli <[email protected]>:
> 
>> Julian et al., -- is there a project/Github wiki, or something similar
>> where I could write up a plan for implementation of OpenGIS functions,
>> their mappings to ESRI library, and have this open for review?
>> 
>> Or should I just open up a new Google Doc. for this?
>> 
>> Edmon
>> 
>> On Wed, Nov 1, 2017 at 5:50 PM, Edmon Begoli <[email protected]> wrote:
>> 
>>> Julian, thanks. Sounds like a plan. I will proceed.
>>> 
>>> Best,
>>> Edmon
>>> 
>>> On Wed, Nov 1, 2017 at 17:12 Julian Hyde <[email protected]> wrote:
>>> 
>>>> Edmon,
>>>> 
>>>> Welcome! Thanks for introducing yourself.
>>>> 
>>>> One area you could help is by reviewing the existing documentation. Run
>>>> through the examples on the web site (e.g. http://calcite.apache.org/
>>>> docs/tutorial.html <http://calcite.apache.org/docs/tutorial.html>) and
>>>> see whether it is consistent and complete. (I.e. does it make sense, and
>>>> does it tell you about everything you would like to know about Calcite,
>> in
>>>> a sensible order.)
>>>> 
>>>> If you would like to write some code, Spatial is an area that you could
>>>> contribute. There are a lot of OpenGIS functions to implement, but they
>> can
>>>> be done one at a time, and usually each takes very little effort because
>>>> there is already an implementations in the underlying ESRI library.
>> Take a
>>>> look at https://github.com/apache/calcite/commit/3e9d3b2 <
>>>> https://github.com/apache/calcite/commit/3e9d3b2> and you’ll see that
>>>> each function requires a small change to just 3 files:
>> GeoFunctions.java,
>>>> spatial.iq, reference.md. Start with say ST_X(geom), which you can base
>>>> upon ST_Z(geom).
>>>> 
>>>> Julian
>>>> 
>>>> 
>>>>> On Oct 30, 2017, at 8:36 PM, Josh Elser <[email protected]> wrote:
>>>>> 
>>>>> Hi Edmon,
>>>>> 
>>>>> Nice to meet you and welcome to the community!
>>>>> 
>>>>> I don't have enough context to throw some well-bounded problems at you
>>>> (I tend to do most of my work on Avatica rather than Calcite directly),
>> but
>>>> I thought it would be nice to say hello anyways :)
>>>>> 
>>>>> Your aspirations and ambition sound great. I look forward to your
>>>> contributions in both code and literature form.
>>>>> 
>>>>> - Josh
>>>>> 
>>>>> On 10/30/17 6:38 PM, Edmon Begoli wrote:
>>>>>> Hello,
>>>>>> I want to introduce myself as a possible new member of the Calcite
>> team
>>>>>> (I know some of you from the Drill team, etc.)
>>>>>> I am a practicing researcher with an interest and the expertise in
>>>>>> advanced data structures, and databases in general (grammars,
>>>>>> architecture, etc.)
>>>>>> I would like to start making contributions, particularly in the
>>>>>> applications of algorithms, or new language formalisms in the areas
>>>>>> that could benefit from those - performance improvements, new
>>>>>> grammatical constructs, parsing, etc.
>>>>>> To this end -- please share with me if there are areas where you feel
>>>>>> Calcite could benefit from new features, or the optimizations.
>>>>>> I do not have time to do lots of heavy lifting coding, but I have
>>>>>> plenty of research and development time and expertise, specially if
>>>>>> you throw a concrete problem at me.
>>>>>> Thank you,
>>>>>> Edmon
>>>>>> P.S. I will start with contributions with the documentation, papers,
>>>>>> presentations, which will allow me to learn the architecture in more
>>>>>> details.
>>>> 
>>>> 
>> 

Reply via email to