Trying to use the new column index feature

not batch_mutate to put data into the indexed column. Jeremiah Jordan Application Developer Morningstar, Inc. Morningstar. Illuminating investing worldwide. +1 312 696-6128 voice jeremiah.jor...@morningstar.com www.morningstar.com This e-mail contains privileged

RE: Trying to use the new column index feature

feature the TProtocolException means you're either (most likely) mixing framed/unframed modes between client/server, or (less likely) creating an obsolete TBinaryProtocol. On Fri, Aug 27, 2010 at 10:13 AM, Jeremiah Jordan jeremiah.jor...@morningstar.com wrote: I am trying to use the new column

RE: [VOTE] 0.7.1 (attempt #2)

So are 0.6.10 and 0.6.11 broken too or did only the 0.7.0 version of https://issues.apache.org/jira/browse/CASSANDRA-1959 break stuff? -Original Message- From: Stu Hood [mailto:stuh...@gmail.com] Sent: Tuesday, February 01, 2011 7:19 PM To: dev@cassandra.apache.org Subject: Re: [VOTE]

Can we get a 0.7.7 release?

Been a while since 0.7.6 and a bunch of stuff has been fixed in JIRA, including https://issues.apache.org/jira/browse/CASSANDRA-2654 which I think may be affecting some of our servers. Jeremiah Jordan Application Developer Morningstar, Inc. Morningstar

Re: [VOTE] Release Apache Cassandra 1.0.3

Ah =). Searching cassandra-dbapi2 on pypi doesn't find it, guess they don't index the homepage links... On Nov 12, 2011, at 10:45 AM, Jonathan Ellis wrote: http://pypi.python.org/pypi/cql/ On Sat, Nov 12, 2011 at 10:29 AM, Jeremiah Jordan jeremiah.jor...@morningstar.com wrote: Someone

Re: How is Cassandra being used?

+1 for a separate jar (and a second download link that doesn't include this jar, though I would make the primary link include it with BIG BOLD PRINT saying it is in there) +1 for a config option to turn off auto-post (defaulted on in the download that has the jar) +1 for a nodetool command to

Re: Ticket CASSANDRA-3578 - Multithreaded CommitLog

Another option is to have multiple threads reading from the queue and writing to their own commit log files. If you have multiple commit log directories with each having its own task writing to it, you can keep the only sequential writes optimization. Multiple writers to one disk only makes

RE: Queries on AuthN and AuthZ for multi tenant Cassandra

10-15 KS should be fine. The issue is when you want to have hundreds or thousands of KS/CF. -Jeremiah -Original Message- From: Subrahmanya Harve [mailto:subrahmanyaha...@gmail.com] Sent: Thursday, February 02, 2012 1:43 AM To: dev@cassandra.apache.org Subject: Re: Queries on AuthN and

RE: RFC: Cassandra Virtual Nodes

neighbor. etc. etc. -Jeremiah Jordan From: Rick Branson [rbran...@datastax.com] Sent: Monday, March 19, 2012 5:16 PM To: dev@cassandra.apache.org Subject: Re: RFC: Cassandra Virtual Nodes I think if we could go back and rebuild Cassandra from scratch, vnodes

Re: Document storage

Sounds interesting to me. I looked into adding protocol buffer support at one point, and it didn't look like it would be too much work. The tricky part was I also wanted to add indexing support for attributes of the inserted protocol buffers. That looked a little trickier, but still not

RE: Document storage

Its not clear what 3647 actually is, there is no code attached, and no real example in it. Aside from that, the reason this would be useful to me (if we could get indexing of attributes working), is that I already have my data in JSON/Thrift/ProtoBuff, depending how large the data is, it isn't

RE: Document storage

Its not clear what 3647 actually is, there is no code attached, and no real example in it. Aside from that, the reason this would be useful to me (if we could get indexing of attributes working), is that I already have my data in JSON/Thrift/ProtoBuff, depending how large the data is, it isn't

RE: Document storage

the majority of the data I pulled back that doesn't belong to o1 and o5 -Jeremiah From: Jonathan Ellis [jbel...@gmail.com] Sent: Thursday, March 29, 2012 11:23 AM To: dev@cassandra.apache.org Subject: Re: Document storage On Thu, Mar 29, 2012 at 9:57 AM, Jeremiah

RE: persistent connection among cluster nodes

Cluster nodes don't talk on 9160. Pretty sure they talk on storage_port: 7000 from the yaml file. -Jeremiah From: Niteesh kumar [nitees...@directi.com] Sent: Tuesday, October 02, 2012 4:52 AM To: dev@cassandra.apache.org Subject: persistent connection

Re: Write Timestamps

How are you doing the write? CQL or Thrift? In thrift, the client specifies the timestamp, and you should always be seeing that as the timestamp. In CQL, the CQL layer on the server adds the timestamp. I am less familiar with the CQL code, maybe something screwy is going on there. 1.1.6 is

RE: Write Timestamps

, October 25, 2012 4:09 PM To: dev@cassandra.apache.org Subject: Re: Write Timestamps On Wed, Oct 24, 2012 at 9:13 PM, Jeremiah Jordan jeremiah.jor...@morningstar.com wrote: How are you doing the write? CQL or Thrift? In thrift, the client specifies the timestamp, and you should always

Re: [VOTE CLOSED] Release Apache Cassandra 2.0.10

Everything should be good now. Thanks! On Aug 11, 2014, at 9:34 AM, Sylvain Lebresne sylv...@datastax.com wrote: Ok, ok, closing this vote for now. We'll re-roll as soon as the pig stuff are fixed. On Fri, Aug 8, 2014 at 10:07 PM, Jeremiah D Jordan jerem...@datastax.com wrote: I'm

Re: Proposal: release 2.2 (based on current trunk) before 3.0 (based on 8099)

Cassandra-jdbc can do cql3 as well as cql2. The rub (and why I would never recommend it) is that it does cql3 over thrift. So you lose out on all the native protocol features. On May 11, 2015, at 2:53 PM, Brian Hess brianmh...@gmail.com wrote: One thing that does jump out at me, though,

Re: COMPACT STORAGE in 4.0?

As I understand it "COMPACT STORAGE" only has meaning in the CQL parser for backwards compatibility as of 3.0. The on disk storage is not affected by its usage. > On Apr 11, 2016, at 3:33 PM, Benedict Elliott Smith > wrote: > > Compact storage should really have been

Re: Proposal - 3.5.1

In the original tick tock plan we would not have kept 4.0.x around. So I am proposing a change for that and then we label the 3.x and 4.x releases as "development releases" or some other thing and have "yearly" LTS releases with .0.x. Those are similar to the previous 1.2/2.0/2.1/2.2 and we

Re: [VOTE] self-assignment of jira tickets

+1 non-binding. That requirement always seemed silly to me. > On Mar 29, 2017, at 8:21 AM, Jason Brown wrote: > > Hey all, > > Following up my thread from a week or two ago ( >

Re: Getting partition min/max timestamp

Don’t forget about deleted and missing data. The bane of all on replica aggregation optimization’s. > On Jan 14, 2018, at 12:07 AM, Jeff Jirsa wrote: > > > You’re right it’s not stored in metadata now. Adding this to metadata isn’t > hard, it’s just hard to do it right

Re: Getting partition min/max timestamp

all, > but also now I get that I should think about the case of data removing. > > I currently don't really care about TTL's, but its the case about I should > think, thx. > > Jeremiah Jordan, thx for notice, but I don't really get what are you mean > about replica aggregation

Re: [DISCUSS] java 9 and the future of cassandra on the jdk

My suggestion would be to keep trunk on the latest LTS by default, but with compatibility with the latest release if possible. Since Oracle LTS releases are every 3 years, I would not want to tie us to that release cycle? So until Java 11 is out that would mean trunk should work under Java 8,

Re: fixing paging state for 4.0

Clients do negotiate the protocol version they use when connecting. If the server bumped the protocol version then this larger paging state could be part of the new protocol version. But that doesn’t solve the problem for existing versions. The special treatment of Integer.MAX_VALUE can be

Re: [DISCUSS] Switch to using GitHub pull requests?

Can’t you currently open a PR with the right commit message, have do review there with all comments posted back to JIRA, run CI on it and then merge it closing the PR? This is the basic workflow you are proposing yes? It is the reviewer and authors job to make sure CI ran and didn’t introduce

Re: [Discuss] num_tokens default in Cassandra 4.0

If you don’t know what you are doing you will have one rack which will also be safe. If you are setting up racks then you most likely read something about doing that, and should also be fine. This discussion has gone off the rails 100 times with what ifs that are “letting perfect be the enemy

[DISCUSS] CEP-18: Improving Modularity

in the CEP. Thanks, -Jeremiah Jordan

Re: [DISCUSS] CEP-17: SSTable format API (CASSANDRA-17056)

Hi Stefan, That idea is not related to this CEP which is about the file formats of the sstables, not file system access. But you should take a look at the work recently committed in https://issues.apache.org/jira/browse/CASSANDRA-16926 to switch to using java.nio.file.Path for file access. This

Re: [DISCUSS] Addition of smile-nlp test dependency for CEP-30

I wonder if it can easily be replaced with Apache open-nlp? It also provides an implementation of GloVe. https://opennlp.apache.org/docs/2.3.0/apidocs/opennlp-tools/opennlp/tools/util/wordvector/Glove.html On Sep 13, 2023 at 1:17:46 PM, Benedict wrote: > There’s a distinction for spotbugs

Re: Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an immediate 5.1-alpha1)

tainer builds on trunk + feature branches, archived for N >> days, and we make that generally known to the dev@ list here so folks >> that want to poke at the current state of trunk or other branches could do >> so with very low friction. We'd probably see more engagement on

Re: Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an immediate 5.1-alpha1)

t; merged with failing or flaky tests. > > Either way, the vote and discussion specifically allow for this to be > overridden. > > 路‍♀️ > > On 31 Oct 2023, at 16:29, Jeremiah Jordan > wrote: > >  > I never said there was a need for green CI for alpha. We d

Re: Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an immediate 5.1-alpha1)

> > My reading of ASF policy is that directing users to CEP preview releases > that are not formally voted upon is not acceptable. The policy you quote > indicates they should be intended only for active participants on dev@, > whereas our explicit intention is to enable them to be advertised to

Re: Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an immediate 5.1-alpha1)

that a > procedural change and rolling things back based on those grounds I'm fine > with that, but we'll need to discuss that and think about the broader > implications since things like changing import ordering, tooling, or other > ecosystem-wide impacting changes (CI systems

Re: Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an immediate 5.1-alpha1)

-5.1 and/or >>>> naming a preview release something other than 5.1-alpha1. >>>> >>>> But… the codebases and release process (and upgrade tests) do not >>>> currently support releases with qualifiers that are not alpha, beta, or >>>> r

Re: Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an immediate 5.1-alpha1)

If we decide to go the route of not merging TCM to the 5.0 branch. Do we actually need to immediately cut a 5.1 branch? Can we work on stabilizing things while it is in trunk and cut the 5.1 branch when we actually think we are near releasing? I don’t see any reason we can not cut “preview”

Re: Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an immediate 5.1-alpha1)

release to create a docker image. > > On Tue, Oct 24, 2023 at 11:54 AM Jeremiah Jordan < > jeremiah.jor...@gmail.com> wrote: > >> If we decide to go the route of not merging TCM to the 5.0 branch. Do we >> actually need to immediately cut a 5.1 branch? Can we work on st

Re: [VOTE] Accept java-driver

+1 nb. Thanks to everyone who has made this happen. On Oct 2, 2023 at 11:52:47 PM, Mick Semb Wever wrote: > The donation of the java-driver is ready for its IP Clearance vote. > https://incubator.apache.org/ip-clearance/cassandra-java-driver.html > > The SGA has been sent to the ASF. This

Re: [VOTE] Accept java-driver

I think this is covered by the grant agreement? https://www.apache.org/licenses/software-grant-template.pdf 2. Licensor represents that, to Licensor's knowledge, Licensor is legally entitled to grant the above license. Licensor agrees to notify the Foundation of any facts or circumstances of

Re: CASSANDRA-18775 (Cassandra supported OSs)

Agreed. -1 on selectively removing any of the libs. But +1 for removing the whole thing if it is no longer used. -Jeremiah On Oct 20, 2023 at 9:28:55 AM, Mick Semb Wever wrote: > Does anyone see any reason _not_ to do this? >> > > > Thanks for bring this to dev@ > > I see reason not to do

Re: Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an immediate 5.1-alpha1)

+1 from me assuming we have tickets and two committer +1’s on them for everything being committed to trunk, and CI is working/passing before it merges. The usual things, but I want to make sure we do not compromise on any of them as we try to “move fast” here. -Jeremiah Jordan On Oct 23, 2023

Re: Thanks to Nate for his service as PMC Chair

Thanks Nate! And welcome to the role Mick! > On Jul 11, 2022, at 7:54 AM, Paulo Motta wrote: > >  > Hi, > > I wanted to announce on behalf of the Apache Cassandra Project Management > Committee (PMC) that Nate McCall (zznate) has stepped down from the PMC chair > role. Thank you Nate for

Re: Single slow node dramatically reduces cluster write throughput regardless of CL

I have seen this same behavior in the past as well and came to the same conclusions of where the issue is. It would be good to write this up in a ticket. Giving people the option of using the DynamicEndpointSnitch to order batch log replica selection could mitigate this exact issue, but may

Re: [DISCUSS] Limiting query results by size (CASSANDRA-11745)

As long as it is valid in the paging protocol to return a short page, but still say “there are more pages”, I think that is fine to do that. For an actual LIMIT that is part of the user query, I think the server must always have returned all data that fits into the LIMIT when all pages have been

Re: Tokenization and SAI query syntax

SASI just uses “=“ for the tokenized equality matching, which is the exact thing this discussion is about changing/not liking. > On Aug 2, 2023, at 7:18 PM, J. D. Jordan wrote: > > I do not think LIKE actually applies here. LIKE is used for prefix, > contains, or suffix searches in SASI

Re: [DISCUSSION] Shall we remove ant javadoc task?

I don’t think anyone wants to remove the javadocs. This thread is about removing the broken ant task which generates html files from them. +1 from me on removing the ant task. If someone feels the task is useful they can always implement one that does not crash and add it back. -Jeremiah On

Re: [Discuss] Repair inside C*

+1 for the side car being the right location. -Jeremiah On Jul 25, 2023 at 1:16:14 PM, Chris Lohfink wrote: > I think a CEP is the next step. Considering the number of companies > involved, this might necessitate several drafts and rounds of discussions. > I appreciate your initiative in

Re: [ANNOUNCEMENT] Expect failures today. Dropping JDK 8 and adding JDK 11

Yes. Great to get this work merged. Thanks to everyone who worked on it and to Ekaterina for leading the charge! -Jeremiah On Jul 24, 2023 at 9:27:10 PM, C. Scott Andreas wrote: > Ekaterina, thank you for spearheading JDK17 support for Apache Cassandra! > Exciting to get to this point. > >

Re: [DISCUSS] Using ACCP or tc-native by default

I had a discussion with Mick on slack. His concern is not with enabling ACCP. His concern is around the testing of the new C* yaml config code which is included in the patch that is used to decide if ACCP should be enabled or not, and if startup should fail if it can’t be enabled. I agree. We

Re: [DISCUSS] Being specific about JDK versions and python lib versions in CI

Yes. -1 on forcing the patch release version, and possibly minor version, for anything that is not absolutely necessary to do so. Especially for things like Java or Python version, I would hope we just install the latest Java 8, Java 11, or Java 17 JDK for the platform the image is built from

Re: CASSANDRA-18554 - mTLS based client and internode authenticators

I like the idea of extending CREATE ROLE rather than adding a brand new ADD IDENTITY syntax. Not sure how that can line up with one to many relationships for an identity, but maybe that can just be done through role hierarchy? In either case, I don’t think IDENTITY related operations should be

Re: [DISCUSS] When to run CheckStyle and other verificiations

+100 I support making generate-idea-files auto setup everything in IntelliJ for you. If you post a diff, I will test it. On this proposal, I don’t really have an opinion one way or the other about what the default is for local "ant jar”, if its slow I will figure out how to turn it off, if its

Re: [DISCUSSIONS] Replace ant eclipse-warnings with CheckerFramework

+1 from me. On Jun 15, 2023 at 1:01:01 PM, Ekaterina Dimitrova wrote: > Hi everyone, > Happy Thursday! > Some time ago, Jacek raised the point that ant eclipse-warnings is generating > too many false positives and not really working as expected. (CASSANDRA-18239) > > Reminder: ant

Re: CASSANDRA-18554 - mTLS based client and internode authenticators

want to give them the power to manage identities. Jeremiah Jordan e. jerem...@datastax.com w. www.datastax.com On Jun 30, 2023 at 1:35:41 PM, Dinesh Joshi wrote: > Yuki, Jeremiah both are fair points. The mental model we're using for > mTLS authentication is slightly different. > > I

Re: [VOTE] CEP-8 Datastax Drivers Donation

+1 nb On Jun 13, 2023 at 9:14:35 AM, Jeremy Hanna wrote: > Calling for a vote on CEP-8 [1]. > > To clarify the intent, as Benjamin said in the discussion thread [2], the > goal of this vote is simply to ensure that the community is in favor of > the donation. Nothing more. > The plan is to

Re: [DISCUSS] Add subscription mangement instructions to user@, dev@ message footers

Here was the thread where it was removed:lists.apache.orgOn Jan 22, 2024, at 12:37 PM, J. D. Jordan wrote:I think we used to have this and removed them because it was breaking the encryption signature on messages or something which meant they were very likely to be treated as spam?Not saying we

Re: Welcome Brad Schoening as Cassandra Committer

Congrats! On Feb 21, 2024 at 2:46:14 PM, Josh McKenzie wrote: > The Apache Cassandra PMC is pleased to announce that Brad Schoening has > accepted > the invitation to become a committer. > > Your work on the integrated python driver, launch script environment, and > tests > has been a big help

Re: Future direction for the row cache and OHC implementation

> > from a maintenance and > integration testing perspective I think it would be better to keep the > ohc in-tree, so we will be aware of any issues immediately after the > full CI run. >From the original email bringing OHC in tree is not an option because the current maintainer is not

Re: Welcome Maxim Muzafarov as Cassandra Committer

Congrats Maxim! Thanks for all of your contributions! On Jan 8, 2024 at 12:19:04 PM, Josh McKenzie wrote: > The Apache Cassandra PMC is pleased to announce that Maxim Muzafarov has > accepted > the invitation to become a committer. > > Thanks for all the hard work and collaboration on the

Re: [DISCUSS] CASSANDRA-18940 SAI post-filtering reads don't update local table latency metrics

Again I am coming at this from the operator/end user perspective. Creating a metrics dashboard, and then I am looking at those metrics to understand what my queries are doing. We have coordinator query level metrics, and then we have lower level table metrics on the replicas. I want to be able

Re: Welcome Mike Adamson as Cassandra committer

Congrats Mike! Thanks for all your work on SAI and Vector index. Well deserved! On Dec 8, 2023 at 8:52:07 AM, Brandon Williams wrote: > Congratulations Mike! > > Kind Regards, > Brandon > > On Fri, Dec 8, 2023 at 8:41 AM Benjamin Lerer wrote: > > > The PMC members are pleased to announce

Re: Welcome Alexandre Dutra, Andrew Tolbert, Bret McGuire, Olivier Michallat as Cassandra Committers

Congrats all! On Apr 17, 2024 at 12:10:11 PM, Benjamin Lerer wrote: > The Apache Cassandra PMC is pleased to announce that Alexandre Dutra, > Andrew Tolbert, Bret McGuire and Olivier Michallat have accepted the > invitation to become committers on the java driver sub-project. > > Thanks for