Hi
My username is RahulPanchal. I would like to contribute to the
Cassandra wiki please.
Thanks
Rahul
Thanks! Based on this and a suggestion by Jon, I'm working on a pluggable
query-logging implementation. Can somebody have a quick look at the last patch
submitted for CASSANDRA-13001 and tell me if I'm heading in the right direction?
Quoting my comment for that file to summarize:
- a new
On 14 March 2017 at 03:55, Jonathan Haddad wrote:
>
> I urge you to try giving the in-tree docs a chance. It may not be the way
> *you* want it but I have to point out that they're the best we've seen in
> Cassandra world. Making them prettier won't help anything.
>
Agreed
Contribution Guide +1
Github WebUI +1
Pull requests +1
Rest: Inspect + Adapt
2017-03-13 19:38 GMT+01:00 Stefan Podkowinski :
> Agreed. Let's not give up on this as quickly. My suggestion is to at
> least provide a getting started guide for writing docs, before
> complaining
Agreed. Let's not give up on this as quickly. My suggestion is to at
least provide a getting started guide for writing docs, before
complaining about too few contributions. I'll try to draft something up
this week.
What people are probably not aware of is how easy it is to contribute
docs through
Ugh... Let's put a few facts out in the open before we start pushing to
move back to the wiki.
First off, take a look at CASSANDRA-8700. There's plenty of reasoning for
why the docs are now located in tree. The TL;DR is:
1. Nobody used the wiki. Like, ever. A handful of edits per year.
2.
Github user MikkelTAndersen commented on the issue:
https://github.com/apache/cassandra/pull/98
If anything is missing please let me know and I will fix it asap...
Den 13. mar. 2017 3.09 PM skrev "Mikkel Andersen" <
mikkel.t.ander...@gmail.com>:
> Thanks Benjamin
The moinmoin wiki was preferred but because of spam, images couldn’t be
attached. The options were to use confluence or have a moderated list of
individuals be approved to update the wiki. The decision was made to go with
the latter because of the preference to stick with moinmoin rather than
The moinmoin wiki was preferred but because of spam, images couldn’t be
attached. The options were to use confluence or have a moderated list of
individuals be approved to update the wiki. The decision was made to go with
the latter because of the preference to stick with moinmoin rather than
Github user MikkelTAndersen commented on the issue:
https://github.com/apache/cassandra/pull/98
I will see what you have already then : )
On Mon, Mar 13, 2017 at 1:44 PM, Benjamin Lerer
wrote:
> @MikkelTAndersen
Github user blerer commented on the issue:
https://github.com/apache/cassandra/pull/98
@MikkelTAndersen Could you also add some unit tests to your patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user MikkelTAndersen commented on the issue:
https://github.com/apache/cassandra/pull/98
Ahh sorry - it seems to complicated, its a simple null check - any chance
you can add it Alex ? I have attached the patch.
On Mon, Mar 13, 2017 at 1:38 PM, Alex Petrov
Github user ifesdjeen commented on the issue:
https://github.com/apache/cassandra/pull/98
Hi @MikkelTAndersen. Cassandra does not use pull requests for Apache
Cassandra. Please use JIRA directly.
You can get more information on the contribution process here
Github user MikkelTAndersen commented on the issue:
https://github.com/apache/cassandra/pull/98
This is a simple fix for when you query with CONTAINS and the collection is
empty (which ends up as null in the database) ... this is a blocking issue for
my company so would appreciate if
GitHub user MikkelTAndersen opened a pull request:
https://github.com/apache/cassandra/pull/98
Fix cassandra 13246
This should fix null pointer if the content of the column is null.
You can merge this pull request into a Git repository by running:
$ git pull
First: I am positively surprised how many guys would like to contribute to
docs.
Some days ago I posted to the dev-list about doc-contribution. I think this
applies here again. From my point of view "in-tree docs" are a good choice
for technical references that go closely with the code
16 matches
Mail list logo