Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jnosql-dev] Proposal: Merge LiquiCouch and add Support forSQL++

Yes, I will add just the interfaces there and whatever is couchbase specific will be implement on couchbase driver. I think I can also implement the Mongo part as well. 

On Wed, Jan 22, 2020, 6:30 PM Werner Keil <werner.keil@xxxxxxx> wrote:

Is LiquiCouch a Driver or Extension to CouchBase or CouchDB Drivers?

 

Either way, we should get something structured into https://github.com/jnosql if we want to invite third party extensions to contribute something there.

Either along the lines of

https://github.com/eclipse/jnosql-diana-driver (probably someting like jnosql-thirdparty-driver or similar)

 

Or an extensions repository a bit like https://github.com/eclipse/jnosql-artemis-extension

 

Werner

 

From: Denis Rosa
Sent: Tuesday, January 21, 2020 19:13
To: jnosql developer discussions
Subject: Re: [jnosql-dev] Proposal: Merge LiquiCouch and add Support forSQL++

 

If possible, I would vote for creating a repo at https://github.com/jnosql .We can get more interest from contributors there.

 

On Thu, Jan 16, 2020 at 7:41 PM Otavio Santana <otaviopolianasantana@xxxxxxxxx> wrote:

That's up to you.
I can create a repository easily and give you access to it.
https://github.com/jnosql

If you decide to create on your repository, please, share here so we can help you with it.

 

On Thu, Jan 16, 2020 at 12:49 PM Denis Rosa <deniswsrosa@xxxxxxxxx> wrote:

Hi Otavio!

 

We could start with proposal 1 then. Should I work on a personal repo first or do you want to create a new repo there already?

 

Best,

 

On Thu, Jan 16, 2020 at 3:28 PM Otavio Santana <otaviopolianasantana@xxxxxxxxx> wrote:

Hey Denis, how are you?
I'm glad to see you around here :)

 

1) I like that, we could create a project initially under JNoSQL umbrella: https://github.com/jnosql
When the project is more mature we can move it under JNoSQL and start the legal process.

2) The SQL++ still with several points to improvements, such as I still not enable to say that all NoSQL implements that. E.g.: Cassandra does not support joins in any way, the same to MongoDB. What we have is a "Least common multiple" of a NoSQL database defined from the type: https://github.com/eclipse/jnosql/blob/master/diana/diana-query/src/main/java/org/eclipse/jnosql/diana/query/Query.g4
The whole point is with SQL++ we have more exceptions than rule, which might be similar to use JPA into NoSQL API.

Yes, we can use Dev.Next to talk about it.

 

On Wed, Jan 15, 2020 at 7:39 AM Denis Rosa <deniswsrosa@xxxxxxxxx> wrote:

Dear All,

 

As I have mentioned on Twitter, I'm super excited about this project, and I would like to propose 2 features that I would like to work on:

 

1) I have created a simple liquibase-like framework for couchbase which helps with schema migration during the application startup (https://github.com/deniswsrosa/liquicouch). My implementation is actually a fork of a similar framework for mongo. We could migrate the framework to JNOSQL and add support for multiple databases.

 

2) Add query support with SQL++

    SQL++(https://arxiv.org/abs/1405.3631) is getting more popular in the NoSQL world and might become the new standard query language for NoSQL databases. Don Chamberlin (the father of SQL) wrote a series of whitepapers and books about it (https://www.couchbase.com/sql-plus-plus-for-sql-users) and a few databases already added support for it natively (Couchbase, AsterixDB, Apache Drill, and Aws-PartiQL ). 

   The language itself resembles a lot JPQL, but with a few extra powers. If you guys never heard about it,  this is a nice place to start: https://query-tutorial.couchbase.com/tutorial/#1 (N1QL is Couchbase's implementation of the SQL++ spec)

   Using some of the SQL++ keywords we could also extend the query support generated by the repository DSL and become more appealing than Spring Data for NoSQL databases.

   Finally, SQL++ should work with both Document and Columnar storages, so it will cover the vast majority of the NoSQL databases out there.

 

Disclaimer: I do work for Couchbase, but I have seen N1QL working really well for us in the past few years, so I do believe that we should push SQL++ to be a standard. Here is also a post from an influential person in the Postgres community talking about SQL++ https://winand.at/newsletter/2019-12/partiql-microsoft-licenses-volcano-model

 

OBS: @Otavio I will also speak at Dev.Next, we could also meet there to discuss more about it.

 

What do you guys think about it?

 

_______________________________________________
jnosql-dev mailing list
jnosql-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jnosql-dev


 

--

Otávio Santana

_______________________________________________
jnosql-dev mailing list
jnosql-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jnosql-dev

_______________________________________________
jnosql-dev mailing list
jnosql-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jnosql-dev


 

--

Otávio Santana

_______________________________________________
jnosql-dev mailing list
jnosql-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jnosql-dev

 

_______________________________________________
jnosql-dev mailing list
jnosql-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jnosql-dev

Back to the top