[ 
https://issues.apache.org/jira/browse/CALCITE-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241464#comment-16241464
 ] 

Edmon Begoli commented on CALCITE-2024:
---------------------------------------

Daniel - that would be most welcome, and you would of course be credited as a 
co-author. 

It could be a very simple benchmark, or a demonstration showing performance of 
a query against native system such as MySQL or Postgres vs. through Calcite, 
and also a NoSQL one like Cassandra or MongoDB.

I could suggest some standard benchmarks, or you choose. I would aim for 
simplicity, and quickness, since we are aiming for Dec. 1 submission deadline 
for SIGMOD. 

We have room for about 2-4 charts, and about 500 words of text before in the 
current shape of the paper. If you decide to participate, please let me know, 
and I will add you to the Overleaf document as collaborator.  

> Submit a journal paper on Calcite to VLDB Journal or ACM SIGMOD Record
> ----------------------------------------------------------------------
>
>                 Key: CALCITE-2024
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2024
>             Project: Calcite
>          Issue Type: Task
>            Reporter: Edmon Begoli
>            Assignee: Edmon Begoli
>            Priority: Minor
>   Original Estimate: 2,352h
>  Remaining Estimate: 2,352h
>
>  Submit an overview paper, with survey, architecture description, and some 
> benchmark components to SIGMOD Record or VLDB Journal.
> SIGMOD Record:
> https://sigmodrecord.org/
> VLDB Journal:
> http://www.vldb.org/vldb_journal/
> I will take a lead on this, create an Overleaf document, and invite all 
> interested co-authors, up to 8 or 10.
> Target for completion on this is Jan-Feb 2018, with 3000-4000 words.  We 
> could also target on of the big conferences, and also look to submit extended 
> journal version of the paper. I will ask Dan Suciu or Sam Madden who preside 
> over both on their advice on this. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to