On Fri, Jun 4, 2021 at 10:32 AM Stefan Miklosovic
wrote:
> I would re-iterate on FQL logging though. What is our decision? Should
> these passwords be clearly visible or we should obfuscate them too?
I don't think it ever makes sense to log a password in plaintext, so
my feeling is we should obfu
Congrats Dinesh!
On Thu, Jun 3, 2021 at 3:59 PM Patrick McFadin wrote:
> This is great. Congratulations Dinesh!
>
> On Thu, Jun 3, 2021 at 11:51 AM Jordan West wrote:
>
> > Congratulations Dinesh!
> >
> > Jordan
> >
> > On Thu, Jun 3, 2021 at 1:40 AM Mick Semb Wever wrote:
> >
> > > Congrats D
Hi,
ok, so this will make it to 4.0 then.
I would re-iterate on FQL logging though. What is our decision? Should
these passwords be clearly visible or we should obfuscate them too?
I am trying to close all remaining questions, while I do get that
passwords in audit are for sure problematic, I do
>
> not ready for production use unless users fully understand what they are
> doing.
This statement stood out to me - in my opinion we should think carefully
about the surface area of the user interfaces on new features before we add
more cognitive burden to our users. We already have plenty of "
+1
On Fri, Jun 4, 2021, 3:53 AM Benjamin Lerer wrote:
> Hi everybody,
>
> There are a significant amount of issues with DROP COMPACT STORAGE that can
> be pretty surprising for users.
> To name a few:
> * Some hidden columns will show up changing the resultset returned for
> wildcard queries
> *
+1, thank you Benjamin! There is already a warning in the docs but marking
it as experimental sounds more reasonable at this point. Thank you for all
your investigations and work done
On Fri, 4 Jun 2021 at 5:43, bened...@apache.org wrote:
> This seems reasonable to me, but it raises a question
+1, please, reclassify it as a bug.
Thank you Stefan
On Fri, 4 Jun 2021 at 9:13, Brandon Williams wrote:
> On Fri, Jun 4, 2021 at 4:32 AM Sam Tunnicliffe wrote:
> > Shipping a brand new, non-experimental feature with a security hole like
> this feels
> > counter to our goal of releases being pr
On Fri, Jun 4, 2021 at 4:32 AM Sam Tunnicliffe wrote:
> Shipping a brand new, non-experimental feature with a security hole like this
> feels
> counter to our goal of releases being prod ready in .0, so I'm +1 on
> including it in
> an rc/ga
I think I have to agree here. We can ship a complete
Thanks!
Why are MVs being treated differently here ?
While node replace was ongoing sstables for MV also got streamed. Is
rebuilding the MV required to ensure consistency between main table and MVs
on the replaced node ?
On Fri, Jun 4, 2021 at 2:25 PM Erick Ramirez
wrote:
> I can't recall if vi
This seems reasonable to me, but it raises a question of roadmap. My
understanding is that we are deprecating compact storage, and will remove it in
a future release (or have already partially removed it? I forget). Do these
issues then constitute a blocking issue for GA, or do we modify our roa
> On 4 Jun 2021, at 03:44, Jonathan Koppenhofer wrote:
>
> +1 to this being a serious bug. As a large user, if we used internal
> passwords, this would completely prevent me from using Cassandra native
> audit log capabilities. Disabling DCL is not a great option, as DCL is
> probably the most
I can't recall if view builds affect the bootstrap but index builds
definitely do. It's a bit late now but you could've run nodetool
compactionstats to see what tasks were running at the time and those need
to complete before the bootstrap is considered complete for the node to go
into UP/NORMAL st
Hi everybody,
There are a significant amount of issues with DROP COMPACT STORAGE that can
be pretty surprising for users.
To name a few:
* Some hidden columns will show up changing the resultset returned for
wildcard queries
* As COMPACT tables did not have primary key liveness there empty rows
in
Hi
We recently replaced a down node containing 90 GB of data. The streaming
process completed within 1 hour as we could see a sufficient amount of data
being streamed on the data disk but the node remained in UJ state and it
took 7 more hours to move to UN state.
We could not figure out anything
14 matches
Mail list logo