Well good to know. Then I think the optional="true" attribute of the java
driver in build.xml is misleading. If you didn't include the java driver,
you're not able to build cassandra as far as I'm trying. I've already suggested
a cassandra-common.jar in another topic (Cassandra client) and I'm
Greetings,
I'm interested in having cassandra client installed separately. I thought that
java classes in cassandra-all.jar are those needed by cassandra server. Also
that the cassandra-clientutil.jar would hold all the necessary classes to run
nodetool and all other sstabletools. My asumptions
Hello list,
why is datastax java-driver so tightly fixed to the cassandra base?
Is there any reason to have it as a shaded dependency?
And what even a shaded dependency is?
I'd be glad for any response.
Thanks Tomas
Thanks guys for joining the discussion, I hope you don't mind if I continue to
argue a bit more.
The core intelligence and functionality of Cassandra server lays in the Java
classes, which reside in jar archives. This is the place where the main
functionality updates take place. To ease the
Greetings,
I've been working with Cassandra for more than a year but I still wonder about
one thing:
To run the server there is a bash script (cassandra) which uses another script
(cassandra.in.sh) which uses yet another bash script (cassandra-env.sh).
What is the reason behind this?
Why there
Thanks for the answer, it did not help much. I have read this several times and
this I already know, It still does not answer the question, why there is the
need for three files instead of a single file. Not to mention multiple
different config files.
All these files are more or less
Hi,
the clock for Python 2.7 is ticking [1], and yes, there are still more than two
years, but sooner or later cqlsh should be ported to Python 3. Is anybody
already working on it or just considers to work on it? What is the long time
plan for cqlsh? Should it be in Python forever or is the
Yeah thanks, I've seen this issue on jira, but it is pretty outdated, and I
wondered if there are any other means of discussing the topic other than the
old jira.
- Original Message -
> Related: https://issues.apache.org/jira/browse/CASSANDRA-10190
>
Thanks Mike,
now I remember this option, but I thought it was set to true by default. Any
reasons why false is the default?
- Original Message -
> Hi Tomas,
>
> Try adding:
>
> start_native_transport: true
>
> to your config.
>
> Cheers,
> MikeA
>
e honestly no idea but it is still defaulting to false in Config.java.
> > I'm assuming it will change to defaulting to true when thrift is finally
> > removed.
> >
> >> On Thu, 29 Jun 2017 at 15:34 Tomas Repik <tre...@redhat.com> wrote:
> >>
> >>
Hello,
I've tried to create a minimal config file that is needed to start Cassandra
server. Is it even possible?
What is the minimal set of options that need to be set in the cassandra.yaml
file in order for Cassandra to run flawlessly.
These are the options I use:
commitlog_sync: periodic
Hi,
while browsing the options for setting up Cassandra at [1] I found an option
`concurrent_batchlog_writes`. This is mentioned only in this documentation but
I could not find it in the config file nor in the source code. Any comments
regarding this are welcome.
Thanks
Tomas
[1]
And yet another glitch in the documentation at:
https://docs.datastax.com/en/cassandra/3.0/cassandra/configuration/configCassandra_yaml.html#configCassandra_yaml__cqlTruncateequest_timeout_in_ms
I guess it should be truncate_timeout_in_ms instead.
Is there a more proper way I should use to
13 matches
Mail list logo
