Welcome!
On 9/1/24 13:16, Maxim Muzafarov wrote:
Thank you all so much, I'm happy to be part of such an active
community and to be able to contribute to the product that is used all
over the world!
On Tue, 9 Jan 2024 at 12:33, Mike Adamson wrote:
Congrats Maxim!!
On Tue, 9 Jan 2024, 10:41
Actually, now that I'm looking at the original email on my browser and not
my phone (and can see the formatting properly), I think we have the
nomenclature backward here. Left-alignment in the printing world means that
text in each cell starts at the left-most column for the cell, but in your
My personal bet is that from the very beginning, Cassandra was more
"number-centric" and right alignment just made more sense back then,
considering strings as an afterthought. Another explanation is that nobody
actually put any work to it to distinguish strings and numbers and it stayed
like
In the ticket itself there's an example of left aligned being better for
prefix strings (e.g. fully qualified class names), and I suspect this is
similarly useful for other things like file paths, etc. I would also agree
with Stefan that it would be nice to know why the current convention was
I would like to know whose idea was it to align it like it is currently done in
the first place. Maybe we are missing something important like why it was done
like that? If there is no reason, we might just start to align it as other DB
offerings do. My initial proposal to support both is more
A configuration option for a cosmetic feature seems like overkill to me, I
don't think which side we align text on is enough to justify (heh) the
overhead. I agree with how Excel and Postgres do it and think we should
follow suit.
Kind Regards,
Brandon
On Tue, Jan 9, 2024 at 9:19 AM Brad
Derek,
I'm proposing a switch or blanket change to a convention of right aligned
text and left aligned numbers in CQLSH.
I took a look at two other examples, Excel and Postgres shell and that's
how they work when displaying tabular data. The Jira was originally to
make right or left alignment
Congratulations Maxim!
On Tue, Jan 9, 2024 at 10:16 AM Benjamin Lerer wrote:
> I am always late to the party. ;-)
> Congrats Maxim!
>
> Le mar. 9 janv. 2024 à 13:16, Maxim Muzafarov a
> écrit :
>
>> Thank you all so much, I'm happy to be part of such an active
>> community and to be able to
I am always late to the party. ;-)
Congrats Maxim!
Le mar. 9 janv. 2024 à 13:16, Maxim Muzafarov a écrit :
> Thank you all so much, I'm happy to be part of such an active
> community and to be able to contribute to the product that is used all
> over the world!
>
> On Tue, 9 Jan 2024 at 12:33,
Just to clarify, per the ticket you're proposing a configuration option to
control this on a per-column basis, correct? Your email makes it sound like
a blanket change.
Cheers,
Derek
On Tue, Jan 9, 2024 at 7:34 AM Brad wrote:
> CQLSH currently left-aligns all output, affecting both numbers
CQLSH currently left-aligns all output, affecting both numbers and text.
While this works well for numbers, a better approach adopted by many is to
left align numbers and right align text.
For example, both Excel and Postgres shell use the later:
psql
# select * from employee;
empid | name
Thank you all so much, I'm happy to be part of such an active
community and to be able to contribute to the product that is used all
over the world!
On Tue, 9 Jan 2024 at 12:33, Mike Adamson wrote:
>
> Congrats Maxim!!
>
> On Tue, 9 Jan 2024, 10:41 Andrés de la Peña, wrote:
>>
>> Congrats,
Additionally, if you have a talk about some underlying technology that
could be applicable across multiple projects submit it or a poster based on
it. We are looking for good cross-project presentations.
Claude
Chair, Community over Code, EU 2024.
On Mon, Jan 8, 2024 at 8:24 PM Paulo Motta
Congrats Maxim!!
On Tue, 9 Jan 2024, 10:41 Andrés de la Peña, wrote:
> Congrats, Maxim!
>
> On Tue, 9 Jan 2024 at 03:45, guo Maxwell wrote:
>
>> Congratulations, Maxim!
>>
>> Francisco Guerrero 于2024年1月9日周二 09:00写道：
>>
>>> Congratulations, Maxim! Well deserved!
>>>
>>> On 2024/01/08 18:19:04
Jon,
That sounds good. Let's make these commands rely on the settings
virtual table and keep the initial changes as minimal as possible.
We've also scheduled a Cassandra Contributor Meeting on January 30th
2024, so I'll prepare some slides with everything we've got so far and
try to prepare
Congrats, Maxim!
On Tue, 9 Jan 2024 at 03:45, guo Maxwell wrote:
> Congratulations, Maxim!
>
> Francisco Guerrero 于2024年1月9日周二 09:00写道：
>
>> Congratulations, Maxim! Well deserved!
>>
>> On 2024/01/08 18:19:04 Josh McKenzie wrote:
>> > The Apache Cassandra PMC is pleased to announce that Maxim
16 matches
Mail list logo
