Github user asfgit closed the pull request at:
https://github.com/apache/cassandra/pull/91
---
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 does not have this feature
enabled and wishes so, or if the feature is en
Github user joaquincasares commented on the issue:
https://github.com/apache/cassandra/pull/90
Super sorry for the delay! I edited the file in Github and didn't realize
that the text was correct and that Github does not use a monospaced font!
I've submitted #91 to fix the issu
GitHub user joaquincasares opened a pull request:
https://github.com/apache/cassandra/pull/91
Fix broken SASI diagrams from PR #90
Addressing the regressions on #90.
I was modifying in Github's view and didn't realize the text was correct
and Github's view does not use a mo
I do miss this from other RDBMSs. If you could come up with a
light-touch way to do this, I think a lot of people would be quite
happy about it.
On Wed, Jan 25, 2017 at 2:02 PM, Corentin Chary
wrote:
> On Wed, Jan 25, 2017 at 9:55 PM, Sam Overton wrote:
>> Hello cassandra-dev,
>>
>> I would like
I think all three of these have merit. Per-CF tracing would be the
most immediately useful (and likely least impactful).
For #3, I like the interface approach over exposing internal APIs. You
can sort of kind of do this with custom QueryProcessor, but having
something specific to tracing would be
Thanks, Sylvain!
--
Michael
On 01/27/2017 02:33 AM, Sylvain Lebresne wrote:
> Fyi, I just committed CASSANDRA-13025 so it's ready for a re-roll as far as
> I can tell.
>
> On Tue, Jan 24, 2017 at 12:31 AM, Michael Shuler
> wrote:
>
>> This vote is being failed for CASSANDRA-13058 (committed a
Fyi, I just committed CASSANDRA-13025 so it's ready for a re-roll as far as
I can tell.
On Tue, Jan 24, 2017 at 12:31 AM, Michael Shuler
wrote:
> This vote is being failed for CASSANDRA-13058 (committed after tentative
> tag) and CASSANDRA-13025 (patch available).
>
> Vote count was 5 binding +1
