[jira] [Created] (CASSANDRA-16107) Remove duplicate line in Cassandra docs about virtual tables limitations
Fábio Takeo Ueno created CASSANDRA-16107: Summary: Remove duplicate line in Cassandra docs about virtual tables limitations Key: CASSANDRA-16107 URL: https://issues.apache.org/jira/browse/CASSANDRA-16107 Project: Cassandra Issue Type: Bug Reporter: Fábio Takeo Ueno Assignee: Fábio Takeo Ueno Lines 81 and 84 of `cassandra/doc/source/new/virtualtable.rst` are exactly the same. This should just remove one of them. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16107) Remove duplicate line in Cassandra docs about virtual tables limitations
[ https://issues.apache.org/jira/browse/CASSANDRA-16107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fábio Takeo Ueno updated CASSANDRA-16107: - Description: Lines 81 and 84 of ``cassandra/doc/source/new/virtualtable.rst`` are exactly the same. This should just remove one of them. (was: Lines 81 and 84 of `cassandra/doc/source/new/virtualtable.rst` are exactly the same. This should just remove one of them.) > Remove duplicate line in Cassandra docs about virtual tables limitations > > > Key: CASSANDRA-16107 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16107 > Project: Cassandra > Issue Type: Bug >Reporter: Fábio Takeo Ueno >Assignee: Fábio Takeo Ueno >Priority: Normal > > Lines 81 and 84 of ``cassandra/doc/source/new/virtualtable.rst`` are exactly > the same. This should just remove one of them. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16107) Remove duplicate line in Cassandra docs about virtual tables limitations
[ https://issues.apache.org/jira/browse/CASSANDRA-16107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fábio Takeo Ueno updated CASSANDRA-16107: - Description: Lines 81 and 84 of cassandra/doc/source/new/virtualtable.rst are exactly the same. This should just remove one of them. (was: Lines 81 and 84 of ``cassandra/doc/source/new/virtualtable.rst`` are exactly the same. This should just remove one of them.) > Remove duplicate line in Cassandra docs about virtual tables limitations > > > Key: CASSANDRA-16107 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16107 > Project: Cassandra > Issue Type: Bug >Reporter: Fábio Takeo Ueno >Assignee: Fábio Takeo Ueno >Priority: Normal > > Lines 81 and 84 of cassandra/doc/source/new/virtualtable.rst are exactly the > same. This should just remove one of them. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16066) Update and rework cassandra-website material to work with Antora
[
https://issues.apache.org/jira/browse/CASSANDRA-16066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Singh updated CASSANDRA-16066:
Attachment: image-2020-09-06-07-17-14-705.png
> Update and rework cassandra-website material to work with Antora
>
>
> Key: CASSANDRA-16066
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16066
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Website
>Reporter: Anthony Grasso
>Priority: Normal
> Attachments: image-2020-09-05-13-24-13-606.png,
> image-2020-09-06-07-17-14-705.png
>
>
> *We want to modernise the way the website is built*
> Rework the cassandra-website repository to generate a UI bundle containing
> resources that Antora will use when generating the Cassandra documents and
> website.
> *The existing method is starting to become dated*
> The documentation and website templates are currently in markdown format.
> Sphinx is used to generate the Cassandra documentation and Jekyll generates
> the website content. One of the major issues with the existing website
> tooling is that the live preview server (render site as it is being updated)
> is really slow. There is a preview server that is really fast, however it is
> unable to detect changes to the content and render automatically.
> *We are migrating the docs to be rendered with Antora*
> The work in CASSANDRA-16029 is converting the document templates to AsciiDoc
> format. Sphinx is being replaced by Antora to generate the documentation
> content. This change has two advantages:
> * More flexibility if the Apache Cassandra documentation look and feel needs
> to be updated or redesigned.
> * More modern look and feel to the documentation.
> *We can use Antora to generate the website as well*
> Antora could also be used to generate the Cassandra website content. As
> suggested on the [mailing
> list|https://www.mail-archive.com/dev@cassandra.apache.org/msg15577.html]
> this would require the existing markdown templates to be converted to
> AsciiDoc as well.
> *Antora needs a UI bundle to style content*
> For Antora to generate the document content and potentially the website
> content it requires a UI bundle (ui-bundle.zip). The UI bundle contains the
> HTML templates (layouts, partials, and helpers), CSS, JavaScript, fonts, and
> (site-wide) images. As such, it provides both the visual theme and user
> interactions for the documentation. Effectively the UI bundle is the
> templates and styling that are applied to the documentation and website
> content.
> *The [cassandra-website|https://github.com/apache/cassandra-website]
> repository can be used to generate the UI bundle*
> All the resources associated with templating and styling the documentation
> and website can be placed in the
> [cassandra-website|https://github.com/apache/cassandra-website] repository.
> In this case the repository would serve two purposes;
> * Generation of the UI bundle resources.
> * Serve the production website content.
> *The [cassandra|https://github.com/apache/cassandra] repository would contain
> the documentation material, while the rest of the non-versioned pages would
> contain that material*
> * All other material that is used to generate documentation would live in
> the [cassandra|https://github.com/apache/cassandra] repository. In this case
> Antora would run on the
> [cassandra/doc|https://github.com/apache/cassandra/doc] directory and pull in
> a UI bundle released on the GitHub
> [cassandra-website|https://github.com/apache/cassandra-website] repository.
> The content generated by Antora using the site.yml file located in this repo
> can be used to preview the docs for review.
> * All other non-versioned material, such as the blogs, development
> instructions, and third-party page would live in the GitHub
> [cassandra-website|https://github.com/apache/cassandra-website] repository.
> Antora will generate the full website using the site.yml located in this
> repo, using both as content sources the material located in both the
> [cassandra|https://github.com/apache/cassandra] and
> [cassandra-website|https://github.com/apache/cassandra-website] repositories.
> *Design, content, and layout would remain the same*
> This proposal means the roles of each repository will change. In addition,
> the workflow to publish material will change as well. However, the website
> design, content, and layout will remain the same.
> As an added bonus the tooling would allow for a live preview server that is
> fast and responsive. However, the time to build and generate the {{nodetool}}
> and Cassandra YAML AssciDoc files will still take in the order of minutes to
> complete.
> *The [cassandra-website|https://github.com/apache
[jira] [Commented] (CASSANDRA-16066) Update and rework cassandra-website material to work with Antora
[
https://issues.apache.org/jira/browse/CASSANDRA-16066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17191242#comment-17191242
]
Rahul Singh commented on CASSANDRA-16066:
-
Acknowledged [~mck] I've updated the diagram. Thanks for the Jira issue related
to the Antora licensing. This was helpful.
With Antora we can keep the UI bundle *and anything to do with antora* only in
cassandra-website. Even though Antora can be used to generate the / and /docs
section of the website and push to asf-staging, it shouldn't need to be a
requirement to generate docs in the release. As mentioned earlier, this can be
achieved with other tools for a basic doc conversion from Asciidoc to HTML or
PDF. e.g. Asciidoctor uses MIT License. We will need to ensure that our
Asciidocs are managed in a way that is conducive to both *Antora* and something
like *Asciidoctor* . (Any non-conflicting licensed tool can be used .. as
mentioned before.)
{noformat}
Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
of the Software, and to permit persons to whom the Software is furnished to do
so, subject to the following conditions:
{noformat}
!image-2020-09-06-07-17-14-705.png!
> Update and rework cassandra-website material to work with Antora
>
>
> Key: CASSANDRA-16066
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16066
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Website
>Reporter: Anthony Grasso
>Priority: Normal
> Attachments: image-2020-09-05-13-24-13-606.png,
> image-2020-09-06-07-17-14-705.png
>
>
> *We want to modernise the way the website is built*
> Rework the cassandra-website repository to generate a UI bundle containing
> resources that Antora will use when generating the Cassandra documents and
> website.
> *The existing method is starting to become dated*
> The documentation and website templates are currently in markdown format.
> Sphinx is used to generate the Cassandra documentation and Jekyll generates
> the website content. One of the major issues with the existing website
> tooling is that the live preview server (render site as it is being updated)
> is really slow. There is a preview server that is really fast, however it is
> unable to detect changes to the content and render automatically.
> *We are migrating the docs to be rendered with Antora*
> The work in CASSANDRA-16029 is converting the document templates to AsciiDoc
> format. Sphinx is being replaced by Antora to generate the documentation
> content. This change has two advantages:
> * More flexibility if the Apache Cassandra documentation look and feel needs
> to be updated or redesigned.
> * More modern look and feel to the documentation.
> *We can use Antora to generate the website as well*
> Antora could also be used to generate the Cassandra website content. As
> suggested on the [mailing
> list|https://www.mail-archive.com/dev@cassandra.apache.org/msg15577.html]
> this would require the existing markdown templates to be converted to
> AsciiDoc as well.
> *Antora needs a UI bundle to style content*
> For Antora to generate the document content and potentially the website
> content it requires a UI bundle (ui-bundle.zip). The UI bundle contains the
> HTML templates (layouts, partials, and helpers), CSS, JavaScript, fonts, and
> (site-wide) images. As such, it provides both the visual theme and user
> interactions for the documentation. Effectively the UI bundle is the
> templates and styling that are applied to the documentation and website
> content.
> *The [cassandra-website|https://github.com/apache/cassandra-website]
> repository can be used to generate the UI bundle*
> All the resources associated with templating and styling the documentation
> and website can be placed in the
> [cassandra-website|https://github.com/apache/cassandra-website] repository.
> In this case the repository would serve two purposes;
> * Generation of the UI bundle resources.
> * Serve the production website content.
> *The [cassandra|https://github.com/apache/cassandra] repository would contain
> the documentation material, while the rest of the non-versioned pages would
> contain that material*
> * All other material that is used to generate documentation would live in
> the [cassandra|https://github.com/apache/cassandra] repository. In this case
> Antora would run on the
> [cassandra/doc|https://github.com/apache/cassandra/doc] directory and pull in
> a UI bundle released on t
[jira] [Updated] (CASSANDRA-16107) Remove duplicate line in Cassandra docs about virtual tables limitations
[ https://issues.apache.org/jira/browse/CASSANDRA-16107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16107: --- Component/s: Documentation/Website > Remove duplicate line in Cassandra docs about virtual tables limitations > > > Key: CASSANDRA-16107 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16107 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Fábio Takeo Ueno >Assignee: Fábio Takeo Ueno >Priority: Normal > > Lines 81 and 84 of cassandra/doc/source/new/virtualtable.rst are exactly the > same. This should just remove one of them. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16066) Update and rework cassandra-website material to work with Antora
[
https://issues.apache.org/jira/browse/CASSANDRA-16066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17191274#comment-17191274
]
Michael Semb Wever commented on CASSANDRA-16066:
The diagram looks great now [~xingh]. Hopefully [~polandll], [~Anthony Grasso],
something like this is feasible ??
> Update and rework cassandra-website material to work with Antora
>
>
> Key: CASSANDRA-16066
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16066
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Website
>Reporter: Anthony Grasso
>Priority: Normal
> Attachments: image-2020-09-05-13-24-13-606.png,
> image-2020-09-06-07-17-14-705.png
>
>
> *We want to modernise the way the website is built*
> Rework the cassandra-website repository to generate a UI bundle containing
> resources that Antora will use when generating the Cassandra documents and
> website.
> *The existing method is starting to become dated*
> The documentation and website templates are currently in markdown format.
> Sphinx is used to generate the Cassandra documentation and Jekyll generates
> the website content. One of the major issues with the existing website
> tooling is that the live preview server (render site as it is being updated)
> is really slow. There is a preview server that is really fast, however it is
> unable to detect changes to the content and render automatically.
> *We are migrating the docs to be rendered with Antora*
> The work in CASSANDRA-16029 is converting the document templates to AsciiDoc
> format. Sphinx is being replaced by Antora to generate the documentation
> content. This change has two advantages:
> * More flexibility if the Apache Cassandra documentation look and feel needs
> to be updated or redesigned.
> * More modern look and feel to the documentation.
> *We can use Antora to generate the website as well*
> Antora could also be used to generate the Cassandra website content. As
> suggested on the [mailing
> list|https://www.mail-archive.com/dev@cassandra.apache.org/msg15577.html]
> this would require the existing markdown templates to be converted to
> AsciiDoc as well.
> *Antora needs a UI bundle to style content*
> For Antora to generate the document content and potentially the website
> content it requires a UI bundle (ui-bundle.zip). The UI bundle contains the
> HTML templates (layouts, partials, and helpers), CSS, JavaScript, fonts, and
> (site-wide) images. As such, it provides both the visual theme and user
> interactions for the documentation. Effectively the UI bundle is the
> templates and styling that are applied to the documentation and website
> content.
> *The [cassandra-website|https://github.com/apache/cassandra-website]
> repository can be used to generate the UI bundle*
> All the resources associated with templating and styling the documentation
> and website can be placed in the
> [cassandra-website|https://github.com/apache/cassandra-website] repository.
> In this case the repository would serve two purposes;
> * Generation of the UI bundle resources.
> * Serve the production website content.
> *The [cassandra|https://github.com/apache/cassandra] repository would contain
> the documentation material, while the rest of the non-versioned pages would
> contain that material*
> * All other material that is used to generate documentation would live in
> the [cassandra|https://github.com/apache/cassandra] repository. In this case
> Antora would run on the
> [cassandra/doc|https://github.com/apache/cassandra/doc] directory and pull in
> a UI bundle released on the GitHub
> [cassandra-website|https://github.com/apache/cassandra-website] repository.
> The content generated by Antora using the site.yml file located in this repo
> can be used to preview the docs for review.
> * All other non-versioned material, such as the blogs, development
> instructions, and third-party page would live in the GitHub
> [cassandra-website|https://github.com/apache/cassandra-website] repository.
> Antora will generate the full website using the site.yml located in this
> repo, using both as content sources the material located in both the
> [cassandra|https://github.com/apache/cassandra] and
> [cassandra-website|https://github.com/apache/cassandra-website] repositories.
> *Design, content, and layout would remain the same*
> This proposal means the roles of each repository will change. In addition,
> the workflow to publish material will change as well. However, the website
> design, content, and layout will remain the same.
> As an added bonus the tooling would allow for a live preview server that is
> fast and responsive. However, the time to build and generate the {{nodetool}}
> and
[jira] [Created] (CASSANDRA-16108) Concurrent Index Memtable implementation using Trie
ZhaoYang created CASSANDRA-16108:
Summary: Concurrent Index Memtable implementation using Trie
Key: CASSANDRA-16108
URL: https://issues.apache.org/jira/browse/CASSANDRA-16108
Project: Cassandra
Issue Type: New Feature
Reporter: ZhaoYang
Replace existing \{{ConcurrentRadixTree}} with Trie implementation for both
numeric index and string index to reduce memory usage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16107) Remove duplicate line in Cassandra docs about virtual tables limitations
[ https://issues.apache.org/jira/browse/CASSANDRA-16107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16107: --- Bug Category: Parent values: Correctness(12982)Level 1 values: API / Semantic Definition(13162) Complexity: Low Hanging Fruit Discovered By: User Report Severity: Low Status: Open (was: Triage Needed) > Remove duplicate line in Cassandra docs about virtual tables limitations > > > Key: CASSANDRA-16107 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16107 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Fábio Takeo Ueno >Assignee: Fábio Takeo Ueno >Priority: Normal > > Lines 81 and 84 of cassandra/doc/source/new/virtualtable.rst are exactly the > same. This should just remove one of them. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16107) Remove duplicate line in Cassandra docs about virtual tables limitations
[ https://issues.apache.org/jira/browse/CASSANDRA-16107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16107: --- Test and Documentation Plan: cassandra.staged.apache.org Status: Patch Available (was: Open) Patch at https://github.com/apache/cassandra/pull/734 > Remove duplicate line in Cassandra docs about virtual tables limitations > > > Key: CASSANDRA-16107 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16107 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Fábio Takeo Ueno >Assignee: Fábio Takeo Ueno >Priority: Normal > > Lines 81 and 84 of cassandra/doc/source/new/virtualtable.rst are exactly the > same. This should just remove one of them. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16107) Remove duplicate line in Cassandra docs about virtual tables limitations
[ https://issues.apache.org/jira/browse/CASSANDRA-16107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16107: --- Reviewers: Michael Semb Wever, Michael Semb Wever (was: Michael Semb Wever) Michael Semb Wever, Michael Semb Wever Status: Review In Progress (was: Patch Available) > Remove duplicate line in Cassandra docs about virtual tables limitations > > > Key: CASSANDRA-16107 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16107 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Fábio Takeo Ueno >Assignee: Fábio Takeo Ueno >Priority: Normal > > Lines 81 and 84 of cassandra/doc/source/new/virtualtable.rst are exactly the > same. This should just remove one of them. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16107) Remove duplicate line in Cassandra docs about virtual tables limitations
[ https://issues.apache.org/jira/browse/CASSANDRA-16107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16107: --- Fix Version/s: 4.0-beta > Remove duplicate line in Cassandra docs about virtual tables limitations > > > Key: CASSANDRA-16107 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16107 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Fábio Takeo Ueno >Assignee: Fábio Takeo Ueno >Priority: Normal > Fix For: 4.0-beta > > > Lines 81 and 84 of cassandra/doc/source/new/virtualtable.rst are exactly the > same. This should just remove one of them. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16072) Reduce thread contention in CommitLogSegment and HintsBuffer by rewriting CAS loops to atomic adds
[
https://issues.apache.org/jira/browse/CASSANDRA-16072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17191367#comment-17191367
]
Michael Semb Wever commented on CASSANDRA-16072:
The patch breaks the CommitLogSegment's closing process (whether capacity
becomes full, or endOfBuffer gets re-assigned before buffer becomes null).
Investigating this further…
> Reduce thread contention in CommitLogSegment and HintsBuffer by rewriting CAS
> loops to atomic adds
> --
>
> Key: CASSANDRA-16072
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16072
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Hints, Local/Commit Log
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 3.11.x, 4.0-beta
>
>
> Follow up to CASSANDRA-15922
> Both CommitLogSegment and HintsBuffer use AtomicIntegers for the current
> offset when allocating. Like in CASSANDRA\-15922 the loops on
> {{.compareAndSet(..)}} can be replaced with atomic adds using the {{.
> getAndAdd(..)}} method.
> In highly contended environments the CAS failures can be high, starving
> writes in a running Cassandra node. On the same cluster CASSANDRA\-15922 was
> found, after CASSANDRA\-15922's fix was deployed, there was still problems
> around commit log flushing and hints. No flamegraph was collected that
> demonstrated the thread contention as clearly as was found in
> CASSANDRA\-15922, but the performance fix proposed here hopefully is obvious
> enough.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-16108) Concurrent Index Memtable implementation using Trie
[
https://issues.apache.org/jira/browse/CASSANDRA-16108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ratcharod reassigned CASSANDRA-16108:
-
Assignee: ratcharod
> Concurrent Index Memtable implementation using Trie
> ---
>
> Key: CASSANDRA-16108
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16108
> Project: Cassandra
> Issue Type: New Feature
>Reporter: ZhaoYang
>Assignee: ratcharod
>Priority: Normal
>
> Replace existing \{{ConcurrentRadixTree}} with Trie implementation for both
> numeric index and string index to reduce memory usage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16108) Concurrent Index Memtable implementation using Trie
[
https://issues.apache.org/jira/browse/CASSANDRA-16108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ratcharod updated CASSANDRA-16108:
--
Resolution: Fixed
Status: Resolved (was: Triage Needed)
> Concurrent Index Memtable implementation using Trie
> ---
>
> Key: CASSANDRA-16108
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16108
> Project: Cassandra
> Issue Type: New Feature
>Reporter: ZhaoYang
>Assignee: ratcharod
>Priority: Normal
>
> Replace existing \{{ConcurrentRadixTree}} with Trie implementation for both
> numeric index and string index to reduce memory usage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16108) Concurrent Index Memtable implementation using Trie
[
https://issues.apache.org/jira/browse/CASSANDRA-16108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ratcharod updated CASSANDRA-16108:
--
Status: Open (was: Resolved)
> Concurrent Index Memtable implementation using Trie
> ---
>
> Key: CASSANDRA-16108
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16108
> Project: Cassandra
> Issue Type: New Feature
>Reporter: ZhaoYang
>Assignee: ratcharod
>Priority: Normal
>
> Replace existing \{{ConcurrentRadixTree}} with Trie implementation for both
> numeric index and string index to reduce memory usage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16082) Add a new jmxtool which can dump what JMX objects exist and diff
[ https://issues.apache.org/jira/browse/CASSANDRA-16082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17191445#comment-17191445 ] Berenguer Blasi commented on CASSANDRA-16082: - [~dcapwell] apologies for the late reply as I was OOO on Friday. PR lgtm assuming CI is good. I would move the ToolRunner POC out of this ticket into CASSANDRA-15591 +1 > Add a new jmxtool which can dump what JMX objects exist and diff > > > Key: CASSANDRA-16082 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16082 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/python >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Time Spent: 4h 10m > Remaining Estimate: 0h > > In order to help validate metric upgrade we first need to know what is new, > what was removed, and what was changed. To help with this, we should add a > new jmxtool which can dump the objects from JMX and diff them. > Once we have this, we can also add a gold list of expected metrics and add > tests to validate these metrics don’t change. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16021) auditlogviewer unit test hardening and docs update
[
https://issues.apache.org/jira/browse/CASSANDRA-16021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17191446#comment-17191446
]
Berenguer Blasi commented on CASSANDRA-16021:
-
Please check {{void
org.apache.cassandra.tools.AuditLogViewerTest.testIgnoreArg()}} and {{void
org.apache.cassandra.tools.AuditLogViewerTest.testFollowNRollArgs()}} for the
ignored assertion. J11 will throw an extra {{WARNING}} that needs removing.
> auditlogviewer unit test hardening and docs update
> --
>
> Key: CASSANDRA-16021
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16021
> Project: Cassandra
> Issue Type: Bug
>Reporter: Berenguer Blasi
>Priority: Normal
>
> During CASSANDRA-15883 / CASSANDRA-15991 it was detected unit test coverage
> for this tool is minimal. There is a unit test to enhance upon under
> {{test/unit/org/apache/cassandra/tools}}. Also docs need updating to reflect
> all available options
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated: Remove duplicate line about virtual table limitations
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/trunk by this push: new 64b338c Remove duplicate line about virtual table limitations 64b338c is described below commit 64b338cbbce6bba70bda696250f3ccf4931b2808 Author: Fábio Ueno AuthorDate: Sat Sep 5 14:55:36 2020 -0300 Remove duplicate line about virtual table limitations patch by Fábio Ueno; reviewed by Mick Semb Wever for CASSANDRA-16107 --- doc/source/new/virtualtables.rst | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/doc/source/new/virtualtables.rst b/doc/source/new/virtualtables.rst index 1a39dc6..1c8766c 100644 --- a/doc/source/new/virtualtables.rst +++ b/doc/source/new/virtualtables.rst @@ -46,7 +46,7 @@ Virtual tables and virtual keyspaces are quite different from regular tables and - Virtual tables are managed by Cassandra and a user cannot run DDL to create new virtual tables or DML to modify existing virtual tables - Virtual tables are created in special keyspaces and not just any keyspace - All existing virtual tables use ``LocalPartitioner``. Since a virtual table is not replicated the partitioner sorts in order of partition keys instead of by their hash. -- Making advanced queries with ``ALLOW FILTERING`` and aggregation functions may be used with virtual tables even though in normal tables we dont recommend it +- Making advanced queries with ``ALLOW FILTERING`` and aggregation functions may be used with virtual tables even though in normal tables we don't recommend it Virtual Keyspaces ^ @@ -81,7 +81,6 @@ Virtual tables and virtual keyspaces have some limitations initially though some - Conditional ``BATCH`` statements cannot include mutations for virtual tables - Cannot include a virtual table statement in a logged batch - Mutations for virtual and regular tables cannot exist in the same batch -- Conditional ``BATCH`` statements cannot include mutations for virtual tables - Cannot create aggregates in virtual keyspaces; but may run aggregate functions on select Listing and Describing Virtual Tables @@ -232,7 +231,7 @@ The ``settings`` table is rather useful and lists all the current configuration (224 rows) -The ``settings`` table can be really useful if yaml file has been changed since startup and dont know running configuration, or to find if they have been modified via jmx/nodetool or virtual tables. +The ``settings`` table can be really useful if yaml file has been changed since startup and don't know running configuration, or to find if they have been modified via jmx/nodetool or virtual tables. Thread Pools Virtual Table - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16107) Remove duplicate line in Cassandra docs about virtual tables limitations
[ https://issues.apache.org/jira/browse/CASSANDRA-16107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16107: --- Status: Ready to Commit (was: Review In Progress) > Remove duplicate line in Cassandra docs about virtual tables limitations > > > Key: CASSANDRA-16107 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16107 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Fábio Takeo Ueno >Assignee: Fábio Takeo Ueno >Priority: Normal > Fix For: 4.0-beta > > > Lines 81 and 84 of cassandra/doc/source/new/virtualtable.rst are exactly the > same. This should just remove one of them. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16107) Remove duplicate line in Cassandra docs about virtual tables limitations
[ https://issues.apache.org/jira/browse/CASSANDRA-16107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16107: --- Fix Version/s: (was: 4.0-beta) 4.0-beta3 Since Version: 4.0-alpha1 Source Control Link: https://github.com/apache/cassandra/commit/64b338cbbce6bba70bda696250f3ccf4931b2808 Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed as [64b338cbbce6bba70bda696250f3ccf4931b2808|https://github.com/apache/cassandra/commit/64b338cbbce6bba70bda696250f3ccf4931b2808] > Remove duplicate line in Cassandra docs about virtual tables limitations > > > Key: CASSANDRA-16107 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16107 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Fábio Takeo Ueno >Assignee: Fábio Takeo Ueno >Priority: Normal > Fix For: 4.0-beta3 > > > Lines 81 and 84 of cassandra/doc/source/new/virtualtable.rst are exactly the > same. This should just remove one of them. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16107) Remove duplicate line in Cassandra docs about virtual tables limitations
[ https://issues.apache.org/jira/browse/CASSANDRA-16107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17191461#comment-17191461 ] Michael Semb Wever commented on CASSANDRA-16107: Thanks [~fabioueno] for reporting and patching it. > Remove duplicate line in Cassandra docs about virtual tables limitations > > > Key: CASSANDRA-16107 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16107 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Fábio Takeo Ueno >Assignee: Fábio Takeo Ueno >Priority: Normal > Fix For: 4.0-beta3 > > Time Spent: 20m > Remaining Estimate: 0h > > Lines 81 and 84 of cassandra/doc/source/new/virtualtable.rst are exactly the > same. This should just remove one of them. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] branch master created (now 0c289bd)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to branch master in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git. at 0c289bd Initialize empty repository This branch includes the following new commits: new 8a03e5c Harry: generator library and extensible framework for fuzz testing Apache Cassandra new 0c289bd Initialize empty repository The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] 02/02: Initialize empty repository
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git commit 0c289bd8aee7a61ff9a85f220b6f7a0886aac828 Author: Alex Petrov AuthorDate: Mon Sep 7 08:27:03 2020 +0200 Initialize empty repository --- README.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/README.txt b/README.txt new file mode 100644 index 000..8b13789 --- /dev/null +++ b/README.txt @@ -0,0 +1 @@ + - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (52df890 -> 458bdb9)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git. discard 52df890 generate docs for f211daf6 new 458bdb9 generate docs for f211daf6 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (52df890) \ N -- N -- N refs/heads/asf-staging (458bdb9) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/doc/4.0-beta3/new/virtualtables.html | 5 ++--- content/doc/4.0-beta3/searchindex.js | 2 +- content/doc/latest/new/virtualtables.html| 5 ++--- content/doc/latest/searchindex.js| 2 +- content/feed.xml | 2 +- src/doc/4.0-beta3/_sources/new/virtualtables.rst.txt | 5 ++--- src/doc/4.0-beta3/new/virtualtables.html | 5 ++--- src/doc/4.0-beta3/searchindex.js | 2 +- 8 files changed, 12 insertions(+), 16 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] 02/02: Initialize empty repository
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a commit to branch test-2 in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git commit 0c289bd8aee7a61ff9a85f220b6f7a0886aac828 Author: Alex Petrov AuthorDate: Mon Sep 7 08:27:03 2020 +0200 Initialize empty repository --- README.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/README.txt b/README.txt new file mode 100644 index 000..8b13789 --- /dev/null +++ b/README.txt @@ -0,0 +1 @@ + - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] branch test-2 created (now 0c289bd)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to branch test-2 in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git. at 0c289bd Initialize empty repository This branch includes the following new commits: new 8a03e5c Harry: generator library and extensible framework for fuzz testing Apache Cassandra new 0c289bd Initialize empty repository The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] branch test-2 updated (0c289bd -> 4dbf969)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to branch test-2 in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git. discard 0c289bd Initialize empty repository discard 8a03e5c Harry: generator library and extensible framework for fuzz testing Apache Cassandra add 4dbf969 Initialize empty repository This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (0c289bd) \ N -- N -- N refs/heads/test-2 (4dbf969) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: LICENSE.txt| 209 - Makefile | 11 - README.md | 538 README.txt | 1 - conf/example.yaml | 74 -- docker/Dockerfile.local| 19 - docker/run-local.sh| 1 - docker/run.sh | 89 -- harry-core/pom.xml | 68 -- harry-core/src/harry/core/Configuration.java | 908 - harry-core/src/harry/core/Run.java | 73 -- .../src/harry/corruptor/AddExtraRowCorruptor.java | 82 -- .../src/harry/corruptor/ChangeValueCorruptor.java | 85 -- .../src/harry/corruptor/HideRowCorruptor.java | 49 -- .../src/harry/corruptor/HideValueCorruptor.java| 74 -- .../harry/corruptor/QueryResponseCorruptor.java| 71 -- harry-core/src/harry/corruptor/RowCorruptor.java | 50 -- .../src/harry/corruptor/ShowValueCorruptor.java| 77 -- harry-core/src/harry/data/ResultSetRow.java| 60 -- harry-core/src/harry/ddl/ColumnSpec.java | 388 - harry-core/src/harry/ddl/SchemaGenerators.java | 295 --- harry-core/src/harry/ddl/SchemaSpec.java | 329 harry-core/src/harry/generators/Bijections.java| 380 - .../src/harry/generators/BooleanGenerator.java | 29 - harry-core/src/harry/generators/Bytes.java | 42 - harry-core/src/harry/generators/Collections.java | 248 -- .../src/harry/generators/DataGenerators.java | 486 --- harry-core/src/harry/generators/Generator.java | 131 --- harry-core/src/harry/generators/Generators.java| 92 --- harry-core/src/harry/generators/PCGFastPure.java | 145 harry-core/src/harry/generators/PcgRSUFast.java| 81 -- .../src/harry/generators/RandomGenerator.java | 87 -- harry-core/src/harry/generators/RngUtils.java | 96 --- .../src/harry/generators/StringBijection.java | 170 harry-core/src/harry/generators/Surjections.java | 158 .../generators/distribution/Distribution.java | 137 harry-core/src/harry/model/DataTracker.java| 123 --- .../src/harry/model/DescriptorSelectorBuilder.java | 104 --- harry-core/src/harry/model/DoNothingModel.java | 38 - harry-core/src/harry/model/ExhaustiveChecker.java | 647 --- harry-core/src/harry/model/Model.java | 69 -- harry-core/src/harry/model/OpSelectors.java| 623 -- harry-core/src/harry/model/QuiescentChecker.java | 110 --- harry-core/src/harry/model/SelectHelper.java | 127 --- .../harry/model/StatelessVisibleRowsChecker.java | 124 --- harry-core/src/harry/model/VisibleRowsChecker.java | 248 -- .../model/clock/ApproximateMonotonicClock.java | 280 --- harry-core/src/harry/model/clock/OffsetClock.java | 61 -- harry-core/src/harry/model/sut/NoOpSut.java| 44 - harry-core/src/harry/model/sut/PrintlnSut.java | 48 -- .../src/harry/model/sut/SystemUnderTest.java | 54 -- .../src/harry/operations/CompiledStatement.java| 56 -- harry-core/src/harry/operations/DeleteHelper.java | 127 --- harry-core/src/harry/operations/Relation.java | 350 harry-core/src/harry/operations/WriteHelper.java | 148 harry-core/src/harry/reconciler/Reconciler.java| 237 -- .../src/harry/runner/AbstractPartitionVisitor.java | 103 --- .../runner/DefaultPartitionVisitorFactory.java | 198 - harry-core/src/harry/runner/DefaultRowVisitor.java | 68 -- harry-core/src/harry/runner/PartitionVisitor.java | 26 - harry-core/src/harry/runner/Query.java | 299 --- harry
[cassandra-harry] branch master updated (0c289bd -> 4dbf969)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to branch master in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git. discard 0c289bd Initialize empty repository discard 8a03e5c Harry: generator library and extensible framework for fuzz testing Apache Cassandra add 4dbf969 Initialize empty repository This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (0c289bd) \ N -- N -- N refs/heads/master (4dbf969) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: LICENSE.txt| 209 - Makefile | 11 - README.md | 538 README.txt | 1 - conf/example.yaml | 74 -- docker/Dockerfile.local| 19 - docker/run-local.sh| 1 - docker/run.sh | 89 -- harry-core/pom.xml | 68 -- harry-core/src/harry/core/Configuration.java | 908 - harry-core/src/harry/core/Run.java | 73 -- .../src/harry/corruptor/AddExtraRowCorruptor.java | 82 -- .../src/harry/corruptor/ChangeValueCorruptor.java | 85 -- .../src/harry/corruptor/HideRowCorruptor.java | 49 -- .../src/harry/corruptor/HideValueCorruptor.java| 74 -- .../harry/corruptor/QueryResponseCorruptor.java| 71 -- harry-core/src/harry/corruptor/RowCorruptor.java | 50 -- .../src/harry/corruptor/ShowValueCorruptor.java| 77 -- harry-core/src/harry/data/ResultSetRow.java| 60 -- harry-core/src/harry/ddl/ColumnSpec.java | 388 - harry-core/src/harry/ddl/SchemaGenerators.java | 295 --- harry-core/src/harry/ddl/SchemaSpec.java | 329 harry-core/src/harry/generators/Bijections.java| 380 - .../src/harry/generators/BooleanGenerator.java | 29 - harry-core/src/harry/generators/Bytes.java | 42 - harry-core/src/harry/generators/Collections.java | 248 -- .../src/harry/generators/DataGenerators.java | 486 --- harry-core/src/harry/generators/Generator.java | 131 --- harry-core/src/harry/generators/Generators.java| 92 --- harry-core/src/harry/generators/PCGFastPure.java | 145 harry-core/src/harry/generators/PcgRSUFast.java| 81 -- .../src/harry/generators/RandomGenerator.java | 87 -- harry-core/src/harry/generators/RngUtils.java | 96 --- .../src/harry/generators/StringBijection.java | 170 harry-core/src/harry/generators/Surjections.java | 158 .../generators/distribution/Distribution.java | 137 harry-core/src/harry/model/DataTracker.java| 123 --- .../src/harry/model/DescriptorSelectorBuilder.java | 104 --- harry-core/src/harry/model/DoNothingModel.java | 38 - harry-core/src/harry/model/ExhaustiveChecker.java | 647 --- harry-core/src/harry/model/Model.java | 69 -- harry-core/src/harry/model/OpSelectors.java| 623 -- harry-core/src/harry/model/QuiescentChecker.java | 110 --- harry-core/src/harry/model/SelectHelper.java | 127 --- .../harry/model/StatelessVisibleRowsChecker.java | 124 --- harry-core/src/harry/model/VisibleRowsChecker.java | 248 -- .../model/clock/ApproximateMonotonicClock.java | 280 --- harry-core/src/harry/model/clock/OffsetClock.java | 61 -- harry-core/src/harry/model/sut/NoOpSut.java| 44 - harry-core/src/harry/model/sut/PrintlnSut.java | 48 -- .../src/harry/model/sut/SystemUnderTest.java | 54 -- .../src/harry/operations/CompiledStatement.java| 56 -- harry-core/src/harry/operations/DeleteHelper.java | 127 --- harry-core/src/harry/operations/Relation.java | 350 harry-core/src/harry/operations/WriteHelper.java | 148 harry-core/src/harry/reconciler/Reconciler.java| 237 -- .../src/harry/runner/AbstractPartitionVisitor.java | 103 --- .../runner/DefaultPartitionVisitorFactory.java | 198 - harry-core/src/harry/runner/DefaultRowVisitor.java | 68 -- harry-core/src/harry/runner/PartitionVisitor.java | 26 - harry-core/src/harry/runner/Query.java | 299 --- harry
[cassandra-harry] branch test-2 deleted (was 4dbf969)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to branch test-2 in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git. was 4dbf969 Initialize empty repository The revisions that were on this branch are still contained in other references; therefore, this change does not discard any commits from the repository. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
