Hi all,
Thank you for the comments and feedbacks.
As Jonathan pointed out, it relies on LWT and uses the protocol
proposed in the paper.
Please read the design document for more detail.
https://github.com/scalar-labs/scalardb/blob/master/docs/design.md
Regarding the licensing, we are thinking
Your dashboards are great. The only challenge is getting all the data to
feed them.
On Tue, Oct 16, 2018 at 1:45 PM Carl Mueller
wrote:
> metadata.csv: that helps a lot, thank you!
>
> On Fri, Oct 5, 2018 at 5:42 AM Alain RODRIGUEZ wrote:
>
>> I feel you for most of the troubles you faced,
metadata.csv: that helps a lot, thank you!
On Fri, Oct 5, 2018 at 5:42 AM Alain RODRIGUEZ wrote:
> I feel you for most of the troubles you faced, I've been facing most of
> them too. Again, Datadog support can probably help you with most of those.
> You should really consider sharing this
Which was followed up by
https://www.researchgate.net/profile/Akon_Dey/publication/282156834_Scalable_Distributed_Transactions_across_Heterogeneous_Stores/links/56058b9608ae5e8e3f32b98d.pdf
On Tue, Oct 16, 2018 at 1:02 PM Jonathan Ellis wrote:
> It looks like it's based on this:
>
It looks like it's based on this:
http://www.vldb.org/pvldb/vol6/p1434-dey.pdf
On Tue, Oct 16, 2018 at 11:37 AM Ariel Weisberg wrote:
> Hi,
>
> Yes this does sound great. Does this rely on Cassandra's internal SERIAL
> consistency and CAS functionality or is that implemented at a higher level?
I think it does use LWT under the hood:
https://github.com/scalar-labs/scalardb/blob/master/src/main/java/com/scalar/database/transaction/consensuscommit/CommitMutationComposer.java#L74-L79
return new Put(base.getPartitionKey(), getClusteringKey(base,
result).orElse(null))
What License did you use? Can we please use Apache 2.0?
On Tue, Oct 16, 2018 at 9:39 AM sankalp kohli
wrote:
> This is awesome and thanks for working on it.
>
> On Tue, Oct 16, 2018 at 9:37 AM Ariel Weisberg wrote:
>
>> Hi,
>>
>> Yes this does sound great. Does this rely on Cassandra's
This is awesome and thanks for working on it.
On Tue, Oct 16, 2018 at 9:37 AM Ariel Weisberg wrote:
> Hi,
>
> Yes this does sound great. Does this rely on Cassandra's internal SERIAL
> consistency and CAS functionality or is that implemented at a higher level?
>
> Regards,
> Ariel
>
> On Tue,
Hi,
Yes this does sound great. Does this rely on Cassandra's internal SERIAL
consistency and CAS functionality or is that implemented at a higher level?
Regards,
Ariel
On Tue, Oct 16, 2018, at 12:31 PM, Jeff Jirsa wrote:
> This is great!
>
> --
> Jeff Jirsa
>
>
> > On Oct 16, 2018, at
This is great!
--
Jeff Jirsa
> On Oct 16, 2018, at 5:47 PM, Hiroyuki Yamada wrote:
>
> Hi all,
>
> # Sorry, I accidentally emailed the following to dev@, so re-sending to here.
>
> We have been working on ACID-compliant transaction library on top of
> Cassandra called Scalar DB,
> and are
Hi all,
# Sorry, I accidentally emailed the following to dev@, so re-sending to here.
We have been working on ACID-compliant transaction library on top of
Cassandra called Scalar DB,
and are pleased to announce the release of v.1.0 RC version in open source.
Hallo,
we work with Cassandra version 3.0.9 and have a problem in a table with TWCS.
The command "nodetool repair" create always new files with old data. This avoid
the delete of the old data.
The layout of the Table is following:
cqlsh> desc stat.spa
CREATE TABLE stat.spa (
region int,
12 matches
Mail list logo
