Bumping into worktree + submodule pain on some harry related work; it looks
like "git worktree" and submodules are not currently fully implemented:
https://git-scm.com/docs/git-worktree#_bugs
BUGS
Multiple checkout in general is still experimental, and the support for
submodules is incomplete.
> I think that Cassandra should have some basic tool available to stress-test
> itself
> I do not think that the current cassandra-stress is completely "useless"
Think there was an implication in my statement I didn't intend. I wasn't
talking about not having *any* stress tool as the reference in
Well this is a completely different kind of discussion, Josh, let's explore it,
shall we?
I think that Cassandra should have some basic tool available to stress-test
itself. Why not? I do not want to depend on some 3rd party tools even if they
might be objectively better. I do not think that th
Hi Jacek,
I took a quick look through the CEP and I think I understand the
implementation you're donating. I don't think that the approach you're
taking and the approach I proposed are contradictory, but I want to make
sure I'm understanding some aspects of the CEP:
1. Is there any mechanism for
> The main issue I see with maintaining the SimpleClient in cassandra-stress is
> the burden it puts on a user to understand the options available when
> connecting with *-mode*:
How frequently do we expect users or devs to use the built-in cassandra-stress
tool? Between tlp-stress and NoSQLBenc
We all agree that we're not suggesting removing SimpleClient from
Cassandra, just from its use in cassandra-stress.
For debugging the native transport protocol, in addition to the standalone
Java Driver, there are the python drivers and ODBC drivers which can be
exercised with cqlsh and Intellij r
