The 'cqlsh' package has been maintained at pypi.org since 2013, see
https://pypi.org/project/cqlsh/#history. There is a solid 10 year history
of support and interest in the Python package distribution for cqlsh and it
has 11K/downloads per week.
A few additions to Jeff's comments:
- The 'cqls
Hi ：
First of all, thank you very much for your work. I have a question: what is
your long-term evolution plan for this project? How to achieve long-term
continuous maintenance of this project? I have encountered some situations
where some people's work is related to a certain project, and then the
Myself and Brad Schoening currently maintain https://pypi.org/project/cqlsh/
which repackages CQLSH that ships with every Cassandra release.
This way:
- anyone who wants a lightweight client to talk to a remote cassandra
can simply `pip install cqlsh` without having to download the full
> On Jun 30, 2023, at 1:09 PM, Jeremiah Jordan wrote:
>
> I don’t think users necessarily need to be able to update their own
> identities. I just don’t want to have to use the super user role. The super
> user role has all power over all things in the data base. I don’t want to
> have to g
> It is surprising to me that we load the identity from the keystore vs
> explicitly setting an expected value in cassandra.yaml. I get that an error
> is thrown if the identity doesn't match those of other nodes in the cluster,
> but does it make sense to prevent startup should the value in the
Looping back to the discussion around keystore usage and shared vs
individual identity. I understand the approach of having a single identity
shared by all nodes in the cluster. Including the entire response here, but
want to focus on the first line.
*The reason we use the keystore is that the nod
sorry, hit send early.
ant test is an interesting one as it seems impractical to run all tests
sequentially, but somebody may want to I suppose.
On Thu, Jul 6, 2023 at 11:53 AM Jon Meredith wrote:
> I think the -Dno-blah settings have usability issues. As they look at
> the property name, not t
I think the -Dno-blah settings have usability issues. As they look at
the property name, not the value, you cannot override them or default
them with ANT_ARGS or by importing to another ant build file. The way
rat.skip does it seems much better using configured value.
Ideally, I would like an eas
Link to the next episode (audio only):
https://drive.google.com/file/d/1HmhtR1stWmtD8gJTFh3gKIye7lQKXN1y/view?usp=sharing
s2e7 - German Eighberger and Theo van Kraay (Microsoft)
(You may have to download it to play)
It will remain in staging for 72 hours, going live (assuming no objections)
by Mo
Hi,
First of all, thank you for all the work!
I personally think that it should be ok to add a new column.
I will be very happy to see this landing in 5.0.
I am personally against porting this patch to 4.1. To be clear, I am sure
you did a great job and my response would be the same to every sing
In my humble opinion, it is better to have only one plain and
straightforward build pipeline for the whole project, with custom
flags used to skip a particular step, than to have multiple pipelines
under the ant tool with multiple endpoints accordingly. I mean, all
the steps need to be lined up, wi
Great discussion, but I feel we still have no conclusion.
I fully support automatically setting up IDE(A) to run the necessary stuff
automatically in a developer-friendly environment, but let it be continued
in a separate thread.
I wouldn't say I like flags, especially if they have to be used o
Hi Maxim,
I went through the PR and added my comments. I think David also reviewed it.
All points you mentioned make sense to me but I humbly think it is necessary to
have at least one additional pair of eyes on this as the patch is relatively
impactful.
I would like to see additional column i
13 matches
Mail list logo
