[jira] [Commented] (CASSANDRA-14493) Test describe statements for aggregates, functions, indexes, schemas, types, and user types
[ https://issues.apache.org/jira/browse/CASSANDRA-14493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528961#comment-16528961 ] Patrick Bannister commented on CASSANDRA-14493: --- We already have tests that cover DESCRIBE statements for indexes and schemas (in the test_describe dtest in cassandra-dtest cqlsh_tests/cqlsh_tests.py). Coverage analysis shows we're exercising those functions after fixing flakiness in test_describe. Also, a "usertype" is not a separate thing from a "type" in the context of DESCRIBE statements, so no separate testing will be needed for describing types vs. describing usertypes. We still need additional testing to exercise describing aggregates, functions, and (user defined) types. > Test describe statements for aggregates, functions, indexes, schemas, types, > and user types > --- > > Key: CASSANDRA-14493 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14493 > Project: Cassandra > Issue Type: Sub-task >Reporter: Patrick Bannister >Priority: Major > Fix For: 4.x > > > Coverage analysis of the cqlsh unittests (pylib/cqlshlib/test/test*.py) and > the dtest cqlsh_tests (cqlsh_tests.py and cqlsh_copy_tests.py) showed no > coverage of functions for describing aggregates, functions, indexes, schemas, > types, or usertypes. > Before we can release a ported cqlsh, we should either create a new test that > exercises these kinds of describe statements, or refute the coverage report > by identifying an existing test for these features. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14552) Website: Add Static Blogging / Article Publishing to cassandra.apache.org
[ https://issues.apache.org/jira/browse/CASSANDRA-14552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528956#comment-16528956 ] C. Scott Andreas commented on CASSANDRA-14552: -- @[~djoshi3] Thanks for taking a look! Can you try walking through the instructions in the README to build? I followed them to build the website prior to making any changes to the repo and during development; they'd worked on two machines for me. Paraphrasing the README: http://svn.apache.org/repos/asf/cassandra/site/src/README – Install rbenv (an easy final step to miss is adding `eval "$(rbenv init -)"` to ~/.bash_profile. – rbenv install 2.4.2 – rbenv local 2.4.2 – gem install jekyll:3.4.3 jekyll-paginate-v2 – make serve Agreed that Dockerizing might make for an easier local development environment for the website. I think that improvements to the build scripts and documentation would be a better fit for proposal in a separate JIRA, though; I'd like to follow the existing build/development process for this ticket rather than making changes to the build environment itself. On that, I do appreciate how minimal the current build process is for the website. I might be an outlier, but don't have Docker or bundler installed on my machines and smiled remembering how simple Jekyll development felt ca. 2010 –– then again, I am also a dinosaur in many respects :-). Would be interested to hear feedback from others who are interested in writing on what makes contribution easiest (/cc [~jolynch]). Re: the SVN repo, that's right – the website is stored in the SVN repo at the URL you shared. Currently, the documentation for updating the website and contributing a post is in the README of the repo itself (similar to CONTRIBUTING.md in the git repo). > Website: Add Static Blogging / Article Publishing to cassandra.apache.org > - > > Key: CASSANDRA-14552 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14552 > Project: Cassandra > Issue Type: Improvement > Components: Documentation and Website >Reporter: C. Scott Andreas >Assignee: C. Scott Andreas >Priority: Minor > Attachments: blog-post-listing.png, blog-post.png, blog.diff > > > To make it easier for members of the community to share what's happening in > Apache Cassandra, advertise meetups, and publish other article-style content, > this patch enables simple blogging functionality via the static > cassandra.apache.org site. > > *How does it work?* > The patch uses Jekyll's built-in static blog functionality to add > article-style publishing. It adds no dynamic content, and does not include > commenting or a mechanism for accepting any user-generated content. It makes > the following changes: > – Adds a new layout file for a blog post listing and single-post detail view > (+ supporting CSS). > – Enables pagination of posts via `jekyll-paginate-v2` > – Adds documentation on how to contribute. > – And fixes a minor documentation issue specifying a Ruby version that > conflicts with earlier guidance in the documentation. > > *How do I write a post?* > The patch includes a /_templates folder with an example post to begin. Blog > posts are written using Markdown. To write a new post, copy the template into > /_posts, rename the file in keeping with the > `MM-DD--blog-post-slug.markdown` convention, add the title/date, and > begin writing. > These pages are generated via the existing build process documented in the > README – `make serve` to preview, `make` to publish. > > *What else should I know?* > The aim of this patch is to make it easy to write and publish. The "/blog" > link is currently hidden from the top nav and no posts are included in this > patch, but this can be enabled once the first article is ready. > > *What's it look like?* > Screenshots of the generated post list view and single-post view attached. > !blog-post-listing.png|width=592,height=619! > > !blog-post.png|width=592,height=619! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-14552) Website: Add Static Blogging / Article Publishing to cassandra.apache.org
[
https://issues.apache.org/jira/browse/CASSANDRA-14552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528952#comment-16528952
]
Dinesh Joshi edited comment on CASSANDRA-14552 at 7/1/18 1:35 AM:
--
Hey [~cscotta], this looks great. {{make serve}} seems to fail for me. I do
have jekyll installed as you can see below -
{noformat}
18:28 $ make serve
make: jekyll: No such file or directory
make: *** [serve] Error 1
18:28 $ jekyll --version
jekyll 3.4.3{noformat}
A few suggestions -
# A Docker container would make it super easy to setup the environment and
make it a low bar to update the toolset. Perhaps consider adding one and
publishing it to Docker Hub?
# Add macOS specific installation instructions using homebrew made it super
easy to acquire ruby, rubyenv, etc.
# Perhaps document that these contributions need to be made against svn -
[https://svn.apache.org/repos/asf/cassandra/site/src/] I could not find a
reference to this. Perhaps I was not looking in the right place?
was (Author: djoshi3):
Hey [~cscotta], this looks great. {{make serve}} seems to fail for me. I do
have jekyll installed as you can see below -
{noformat}
18:28 $ make serve
make: jekyll: No such file or directory
make: *** [serve] Error 1
18:28 $ jekyll --version
jekyll 3.4.3{noformat}
A few suggestions -
# A Docker container would make it super easy to setup the environment and
make it a low bar to update the toolset. Perhaps consider adding one and
publishing it to Docker Hub?
# Add macOS specific installation instructions using homebrew made it super
easy to acquire ruby, rubyenv, etc.
> Website: Add Static Blogging / Article Publishing to cassandra.apache.org
> -
>
> Key: CASSANDRA-14552
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14552
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation and Website
>Reporter: C. Scott Andreas
>Assignee: C. Scott Andreas
>Priority: Minor
> Attachments: blog-post-listing.png, blog-post.png, blog.diff
>
>
> To make it easier for members of the community to share what's happening in
> Apache Cassandra, advertise meetups, and publish other article-style content,
> this patch enables simple blogging functionality via the static
> cassandra.apache.org site.
>
> *How does it work?*
> The patch uses Jekyll's built-in static blog functionality to add
> article-style publishing. It adds no dynamic content, and does not include
> commenting or a mechanism for accepting any user-generated content. It makes
> the following changes:
> – Adds a new layout file for a blog post listing and single-post detail view
> (+ supporting CSS).
> – Enables pagination of posts via `jekyll-paginate-v2`
> – Adds documentation on how to contribute.
> – And fixes a minor documentation issue specifying a Ruby version that
> conflicts with earlier guidance in the documentation.
>
> *How do I write a post?*
> The patch includes a /_templates folder with an example post to begin. Blog
> posts are written using Markdown. To write a new post, copy the template into
> /_posts, rename the file in keeping with the
> `MM-DD--blog-post-slug.markdown` convention, add the title/date, and
> begin writing.
> These pages are generated via the existing build process documented in the
> README – `make serve` to preview, `make` to publish.
>
> *What else should I know?*
> The aim of this patch is to make it easy to write and publish. The "/blog"
> link is currently hidden from the top nav and no posts are included in this
> patch, but this can be enabled once the first article is ready.
>
> *What's it look like?*
> Screenshots of the generated post list view and single-post view attached.
> !blog-post-listing.png|width=592,height=619!
>
> !blog-post.png|width=592,height=619!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14552) Website: Add Static Blogging / Article Publishing to cassandra.apache.org
[
https://issues.apache.org/jira/browse/CASSANDRA-14552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528952#comment-16528952
]
Dinesh Joshi commented on CASSANDRA-14552:
--
Hey [~cscotta], this looks great. {{make serve}} seems to fail for me. I do
have jekyll installed as you can see below -
{noformat}
18:28 $ make serve
make: jekyll: No such file or directory
make: *** [serve] Error 1
18:28 $ jekyll --version
jekyll 3.4.3{noformat}
A few suggestions -
# A Docker container would make it super easy to setup the environment and
make it a low bar to update the toolset. Perhaps consider adding one and
publishing it to Docker Hub?
# Add macOS specific installation instructions using homebrew made it super
easy to acquire ruby, rubyenv, etc.
> Website: Add Static Blogging / Article Publishing to cassandra.apache.org
> -
>
> Key: CASSANDRA-14552
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14552
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation and Website
>Reporter: C. Scott Andreas
>Assignee: C. Scott Andreas
>Priority: Minor
> Attachments: blog-post-listing.png, blog-post.png, blog.diff
>
>
> To make it easier for members of the community to share what's happening in
> Apache Cassandra, advertise meetups, and publish other article-style content,
> this patch enables simple blogging functionality via the static
> cassandra.apache.org site.
>
> *How does it work?*
> The patch uses Jekyll's built-in static blog functionality to add
> article-style publishing. It adds no dynamic content, and does not include
> commenting or a mechanism for accepting any user-generated content. It makes
> the following changes:
> – Adds a new layout file for a blog post listing and single-post detail view
> (+ supporting CSS).
> – Enables pagination of posts via `jekyll-paginate-v2`
> – Adds documentation on how to contribute.
> – And fixes a minor documentation issue specifying a Ruby version that
> conflicts with earlier guidance in the documentation.
>
> *How do I write a post?*
> The patch includes a /_templates folder with an example post to begin. Blog
> posts are written using Markdown. To write a new post, copy the template into
> /_posts, rename the file in keeping with the
> `MM-DD--blog-post-slug.markdown` convention, add the title/date, and
> begin writing.
> These pages are generated via the existing build process documented in the
> README – `make serve` to preview, `make` to publish.
>
> *What else should I know?*
> The aim of this patch is to make it easy to write and publish. The "/blog"
> link is currently hidden from the top nav and no posts are included in this
> patch, but this can be enabled once the first article is ready.
>
> *What's it look like?*
> Screenshots of the generated post list view and single-post view attached.
> !blog-post-listing.png|width=592,height=619!
>
> !blog-post.png|width=592,height=619!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Resolved] (CASSANDRA-14490) Test displaying CJK languages
[ https://issues.apache.org/jira/browse/CASSANDRA-14490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Bannister resolved CASSANDRA-14490. --- Resolution: Not A Problem The unused CJK related functions of wcwidth are not necessary for displaying CJK text in Unicode. > Test displaying CJK languages > - > > Key: CASSANDRA-14490 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14490 > Project: Cassandra > Issue Type: Sub-task >Reporter: Patrick Bannister >Priority: Major > Labels: cqlsh, test > Fix For: 4.0.x > > > Coverage analysis of cqlsh tests showed no coverage of wcwidth functions > related to displaying CJK languages. Before releasing a port, we should > identify or create a test that exercises code paths for displaying CJK > language data in cqlsh. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14490) Test displaying CJK languages
[ https://issues.apache.org/jira/browse/CASSANDRA-14490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528939#comment-16528939 ] Patrick Bannister commented on CASSANDRA-14490: --- Looking at this closer: there is actually nothing in cqlsh that can use the cjk specific functions of wcwidth. Furthermore, those functions are only intended to support users who want to migrate to Unicode from a legacy CJK encoding. Nevertheless, I've added test_cjk_output to TestCqlshSmoke in cqlsh_tests/cqlsh_tests.py in the developmental branch for the port. > Test displaying CJK languages > - > > Key: CASSANDRA-14490 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14490 > Project: Cassandra > Issue Type: Sub-task >Reporter: Patrick Bannister >Priority: Major > Labels: cqlsh, test > Fix For: 4.0.x > > > Coverage analysis of cqlsh tests showed no coverage of wcwidth functions > related to displaying CJK languages. Before releasing a port, we should > identify or create a test that exercises code paths for displaying CJK > language data in cqlsh. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14553) Document troubleshooting page
[ https://issues.apache.org/jira/browse/CASSANDRA-14553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528930#comment-16528930 ] C. Scott Andreas commented on CASSANDRA-14553: -- @[~jolynch] Thanks, sounds great! > Document troubleshooting page > - > > Key: CASSANDRA-14553 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14553 > Project: Cassandra > Issue Type: Improvement > Components: Documentation and Website >Reporter: Joseph Lynch >Priority: Minor > Labels: Documentation > > Currently the [troubleshooting > docs|http://cassandra.apache.org/doc/latest/troubleshooting/] are blank. As > much as I like to believe Cassandra never has any problems I was thinking of > writing up a troubleshooting page focussing on: > # Finding the hosts(s) that are behaving badly (common error messages) > # Which logs exist, where they are, and what to look for in which log > (common error messages, gc logs, etc) > # Which nodetool commands can give you more information > # Java/Operating systems tools that can help dive deep into performance > issues (jstat, top, iostat, cachestat, etc) > Since this is going to be a fairly lengthy page I wanted to get a jira going > in case someone else had ideas or had already started. Also if there are any > large areas I missed above please comment here and I can include them. > [~cscotta] fyi -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-14553) Document troubleshooting page
Joseph Lynch created CASSANDRA-14553: Summary: Document troubleshooting page Key: CASSANDRA-14553 URL: https://issues.apache.org/jira/browse/CASSANDRA-14553 Project: Cassandra Issue Type: Improvement Components: Documentation and Website Reporter: Joseph Lynch Currently the [troubleshooting docs|http://cassandra.apache.org/doc/latest/troubleshooting/] are blank. As much as I like to believe Cassandra never has any problems I was thinking of writing up a troubleshooting page focussing on: # Finding the hosts(s) that are behaving badly (common error messages) # Which logs exist, where they are, and what to look for in which log (common error messages, gc logs, etc) # Which nodetool commands can give you more information # Java/Operating systems tools that can help dive deep into performance issues (jstat, top, iostat, cachestat, etc) Since this is going to be a fairly lengthy page I wanted to get a jira going in case someone else had ideas or had already started. Also if there are any large areas I missed above please comment here and I can include them. [~cscotta] fyi -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-9608) Support Java 11
[
https://issues.apache.org/jira/browse/CASSANDRA-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528880#comment-16528880
]
Jason Brown edited comment on CASSANDRA-9608 at 6/30/18 8:21 PM:
-
Added more comments to the PR, and have the following:
* JMXServerUtils - I'm not sure sure what to do with this one. I'm not
thrilled with just using reflection to get at an instance of
{{JMXPluggableAuthenticator}}, expecially when the behavior it provides doesn't
appear to be anything special. Further, it looks like {{AuthenticationProxy}}
does most of the same functionality anyway. That being said, I am not a
JMX/JAAS expert in any way, and I'd love [~beobal]'s input on whether we could
eliminate {{JMXPluggableAuthenticatorWrapper}} in lieu of something similar to
{{AuthenticationProxy}}. This being said, I would be OK-ish if we stick with
the existing {{JMXPluggableAuthenticator}} as it ties directly into the jdk's
JMX subsystem and changes that happen there we would just get out of the box,
rather than needing to attempt feature parity with it.
* build.xml - we used to reference the jdkoverride in the javac step of the
{{build}} task. That seems to have been lost from the current build.xml file.
Further, it's not entirely clear to me what that jdkoverride is actually doing,
particularly in the java compilation step. I'll look into purpose of the sole
class in that directory, CRC32.class
** UPDATE : looks like the CRC32.class was related to CASSANDRA-8614, which
tried to optimize for java8 jvms (over java7). Thus, I think we can eliminate
this jdkoverride thing altogether - the build.xml variable reference and the
dummy class file in {{src/jdkoverrides}}.
Review ongoing ...
was (Author: jasobrown):
Added more comments to the PR, and have the following:
* JMXServerUtils - I'm not sure sure what to do with this one. I'm not
thrilled with just using reflection to get at an instance of
{{JMXPluggableAuthenticator}}, expecially when the behavior it provides doesn't
appear to be anything special. Further, it looks like {{AuthenticationProxy}}
does most of the same functionality anyway. That being said, I am not a
JMX/JAAS expert in any way, and I'd love [~beobal]'s input on whether we could
eliminate {{JMXPluggableAuthenticatorWrapper}} in lieu of something similar to
{{AuthenticationProxy}}. This being said, I would be OK-ish if we stick with
the existing {{JMXPluggableAuthenticator}} as it ties directly into the jdk's
JMX subsystem and changes that happen there we would just get out of the box,
rather than needing to attempt feature parity with it.
* build.xml - we used to reference the jdkoverride in the javac step of the
{{build}} task. That seems to have been lost from the current build.xml file.
Further, it's not entirely clear to me what that jdkoverride is actually doing,
particularly in the java compilation step. I'll look into purpose of the sole
class in that directory, CRC32.class
Review ongoing ...
> Support Java 11
> ---
>
> Key: CASSANDRA-9608
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9608
> Project: Cassandra
> Issue Type: Task
>Reporter: Robert Stupp
>Assignee: Robert Stupp
>Priority: Minor
> Fix For: 4.x
>
> Attachments: jdk_9_10.patch
>
>
> This ticket is intended to group all issues found to support Java 9 in the
> future.
> From what I've found out so far:
> * Maven dependency {{com.sun:tools:jar:0}} via cobertura cannot be resolved.
> It can be easily solved using this patch:
> {code}
> - artifactId="cobertura"/>
> + artifactId="cobertura">
> +
> +
> {code}
> * Another issue is that {{sun.misc.Unsafe}} no longer contains the methods
> {{monitorEnter}} + {{monitorExit}}. These methods are used by
> {{o.a.c.utils.concurrent.Locks}} which is only used by
> {{o.a.c.db.AtomicBTreeColumns}}.
> I don't mind to start working on this yet since Java 9 is in a too early
> development phase.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-9608) Support Java 11
[
https://issues.apache.org/jira/browse/CASSANDRA-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528880#comment-16528880
]
Jason Brown edited comment on CASSANDRA-9608 at 6/30/18 8:10 PM:
-
Added more comments to the PR, and have the following:
* JMXServerUtils - I'm not sure sure what to do with this one. I'm not
thrilled with just using reflection to get at an instance of
{{JMXPluggableAuthenticator}}, expecially when the behavior it provides doesn't
appear to be anything special. Further, it looks like {{AuthenticationProxy}}
does most of the same functionality anyway. That being said, I am not a
JMX/JAAS expert in any way, and I'd love [~beobal]'s input on whether we could
eliminate {{JMXPluggableAuthenticatorWrapper}} in lieu of something similar to
{{AuthenticationProxy}}. This being said, I would be OK-ish if we stick with
the existing {{JMXPluggableAuthenticator}} as it ties directly into the jdk's
JMX subsystem and changes that happen there we would just get out of the box,
rather than needing to attempt feature parity with it.
* build.xml - we used to reference the jdkoverride in the javac step of the
{{build}} task. That seems to have been lost from the current build.xml file.
Further, it's not entirely clear to me what that jdkoverride is actually doing,
particularly in the java compilation step. I'll look into purpose of the sole
class in that directory, CRC32.class
Review ongoing ...
was (Author: jasobrown):
Added more comments to the PR, and have the following:
* JMXServerUtils - I'm not sure sure what to do with this one. I'm not
thrilled with just using reflection to get at an instance of
{{JMXPluggableAuthenticator}}, expecially when the behavior it provides doesn't
appear to be anything special. Further, it looks like {{AuthenticationProxy}}
does most of the same functionality anyway. That being said, I am not a
JMX/JAAS expert in any way, and I'd love [~beobal]'s input on whether we could
eliminate {{JMXPluggableAuthenticatorWrapper}} in lieu of something similar to
{{AuthenticationProxy}}. This being said, I would be OK-ish if we stick with
the existing {{JMXPluggableAuthenticator}} as it ties directly into the jdk's
JMX subsystem and changes that happen there we would just get out of the box,
rather than needing to attempt feature parity with it.
Review ongoing ...
> Support Java 11
> ---
>
> Key: CASSANDRA-9608
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9608
> Project: Cassandra
> Issue Type: Task
>Reporter: Robert Stupp
>Assignee: Robert Stupp
>Priority: Minor
> Fix For: 4.x
>
> Attachments: jdk_9_10.patch
>
>
> This ticket is intended to group all issues found to support Java 9 in the
> future.
> From what I've found out so far:
> * Maven dependency {{com.sun:tools:jar:0}} via cobertura cannot be resolved.
> It can be easily solved using this patch:
> {code}
> - artifactId="cobertura"/>
> + artifactId="cobertura">
> +
> +
> {code}
> * Another issue is that {{sun.misc.Unsafe}} no longer contains the methods
> {{monitorEnter}} + {{monitorExit}}. These methods are used by
> {{o.a.c.utils.concurrent.Locks}} which is only used by
> {{o.a.c.db.AtomicBTreeColumns}}.
> I don't mind to start working on this yet since Java 9 is in a too early
> development phase.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-9608) Support Java 11
[
https://issues.apache.org/jira/browse/CASSANDRA-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528880#comment-16528880
]
Jason Brown edited comment on CASSANDRA-9608 at 6/30/18 8:07 PM:
-
Added more comments to the PR, and have the following:
* JMXServerUtils - I'm not sure sure what to do with this one. I'm not
thrilled with just using reflection to get at an instance of
{{JMXPluggableAuthenticator}}, expecially when the behavior it provides doesn't
appear to be anything special. Further, it looks like {{AuthenticationProxy}}
does most of the same functionality anyway. That being said, I am not a
JMX/JAAS expert in any way, and I'd love [~beobal]'s input on whether we could
eliminate {{JMXPluggableAuthenticatorWrapper}} in lieu of something similar to
{{AuthenticationProxy}}. This being said, I would be OK-ish if we stick with
the existing {{JMXPluggableAuthenticator}} as it ties directly into the jdk's
JMX subsystem and changes that happen there we would just get out of the box,
rather than needing to attempt feature parity with it.
Review ongoing ...
was (Author: jasobrown):
Added more comments to the PR, and have the following:
* JMXServerUtils - I'm not sure sure what to do with this one. I'm not
thrilled with just using reflection to get at an instance of
\{{JMXPluggableAuthenticator}}, expecially when the behavior it provides
doesn't appear to be anything special. Further, it looks like
\{{AuthenticationProxy}} does most of the same functionality anyway. That being
said, I am not a JMX/JAAS expert in any way, and I'd love @beobal's input on
whether we could eliminate \{{JMXPluggableAuthenticatorWrapper}} in lieu of
something similar to \{{AuthenticationProxy}}. This being said, I would be
OK-ish if we stick with the existing \{{JMXPluggableAuthenticator}} as it ties
directly into the jdk's JMX subsystem and changes that happen there we would
just get out of the box, rather than needing to attempt feature parity with it.
Review ongoing ...
> Support Java 11
> ---
>
> Key: CASSANDRA-9608
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9608
> Project: Cassandra
> Issue Type: Task
>Reporter: Robert Stupp
>Assignee: Robert Stupp
>Priority: Minor
> Fix For: 4.x
>
> Attachments: jdk_9_10.patch
>
>
> This ticket is intended to group all issues found to support Java 9 in the
> future.
> From what I've found out so far:
> * Maven dependency {{com.sun:tools:jar:0}} via cobertura cannot be resolved.
> It can be easily solved using this patch:
> {code}
> - artifactId="cobertura"/>
> + artifactId="cobertura">
> +
> +
> {code}
> * Another issue is that {{sun.misc.Unsafe}} no longer contains the methods
> {{monitorEnter}} + {{monitorExit}}. These methods are used by
> {{o.a.c.utils.concurrent.Locks}} which is only used by
> {{o.a.c.db.AtomicBTreeColumns}}.
> I don't mind to start working on this yet since Java 9 is in a too early
> development phase.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-9608) Support Java 11
[
https://issues.apache.org/jira/browse/CASSANDRA-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528880#comment-16528880
]
Jason Brown commented on CASSANDRA-9608:
Added more comments to the PR, and have the following:
* JMXServerUtils - I'm not sure sure what to do with this one. I'm not
thrilled with just using reflection to get at an instance of
\{{JMXPluggableAuthenticator}}, expecially when the behavior it provides
doesn't appear to be anything special. Further, it looks like
\{{AuthenticationProxy}} does most of the same functionality anyway. That being
said, I am not a JMX/JAAS expert in any way, and I'd love @beobal's input on
whether we could eliminate \{{JMXPluggableAuthenticatorWrapper}} in lieu of
something similar to \{{AuthenticationProxy}}. This being said, I would be
OK-ish if we stick with the existing \{{JMXPluggableAuthenticator}} as it ties
directly into the jdk's JMX subsystem and changes that happen there we would
just get out of the box, rather than needing to attempt feature parity with it.
Review ongoing ...
> Support Java 11
> ---
>
> Key: CASSANDRA-9608
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9608
> Project: Cassandra
> Issue Type: Task
>Reporter: Robert Stupp
>Assignee: Robert Stupp
>Priority: Minor
> Fix For: 4.x
>
> Attachments: jdk_9_10.patch
>
>
> This ticket is intended to group all issues found to support Java 9 in the
> future.
> From what I've found out so far:
> * Maven dependency {{com.sun:tools:jar:0}} via cobertura cannot be resolved.
> It can be easily solved using this patch:
> {code}
> - artifactId="cobertura"/>
> + artifactId="cobertura">
> +
> +
> {code}
> * Another issue is that {{sun.misc.Unsafe}} no longer contains the methods
> {{monitorEnter}} + {{monitorExit}}. These methods are used by
> {{o.a.c.utils.concurrent.Locks}} which is only used by
> {{o.a.c.db.AtomicBTreeColumns}}.
> I don't mind to start working on this yet since Java 9 is in a too early
> development phase.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14552) Website: Add Static Blogging / Article Publishing to cassandra.apache.org
[ https://issues.apache.org/jira/browse/CASSANDRA-14552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] C. Scott Andreas updated CASSANDRA-14552: - Description: To make it easier for members of the community to share what's happening in Apache Cassandra, advertise meetups, and publish other article-style content, this patch enables simple blogging functionality via the static cassandra.apache.org site. *How does it work?* The patch uses Jekyll's built-in static blog functionality to add article-style publishing. It adds no dynamic content, and does not include commenting or a mechanism for accepting any user-generated content. It makes the following changes: – Adds a new layout file for a blog post listing and single-post detail view (+ supporting CSS). – Enables pagination of posts via `jekyll-paginate-v2` – Adds documentation on how to contribute. – And fixes a minor documentation issue specifying a Ruby version that conflicts with earlier guidance in the documentation. *How do I write a post?* The patch includes a /_templates folder with an example post to begin. Blog posts are written using Markdown. To write a new post, copy the template into /_posts, rename the file in keeping with the `MM-DD--blog-post-slug.markdown` convention, add the title/date, and begin writing. These pages are generated via the existing build process documented in the README – `make serve` to preview, `make` to publish. *What else should I know?* The aim of this patch is to make it easy to write and publish. The "/blog" link is currently hidden from the top nav and no posts are included in this patch, but this can be enabled once the first article is ready. *What's it look like?* Screenshots of the generated post list view and single-post view attached. !blog-post-listing.png|width=592,height=619! !blog-post.png|width=592,height=619! was: To make it easier for members of the community to share what's happening in Apache Cassandra, advertise meetups, and publish other article-style content, this patch enables simple blogging functionality via the static cassandra.apache.org site. *How does it work?* The patch uses Jekyll's built-in static blog functionality to add article-style publishing. It adds no dynamic content, and does not include commenting or a mechanism for accepting any user-generated content. It makes the following changes: – Adds a new layout file for a blog post listing and single-post detail view (+ supporting CSS). – Enables pagination of posts via `jekyll-paginate-v2` – Adds documentation on how to contribute. – And fixes a minor documentation issue specifying a Ruby version that conflicts with earlier guidance in the documentation. *How do I write a post?* The patch includes a /_templates folder with an example post to begin. Blog posts are written using Markdown. To write a new post, copy the template into /_posts, rename the file in keeping with the `MM-DD--blog-post-slug.markdown` convention, add the title/date, and begin writing. These pages are generated via the existing build process documented in the README – `make serve` to preview, `make` to publish. *What else should I know?* The aim of this patch is to make it easy to write and publish. The "/blog" link is currently hidden from the top nav and no posts are included in this patch, but this can be enabled once the first article is ready. *What's it look like?* Screenshots of the generated post list view and single-post view attached. !blog-post-listing.png! !blog-post.png! > Website: Add Static Blogging / Article Publishing to cassandra.apache.org > - > > Key: CASSANDRA-14552 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14552 > Project: Cassandra > Issue Type: Improvement > Components: Documentation and Website >Reporter: C. Scott Andreas >Assignee: C. Scott Andreas >Priority: Minor > Attachments: blog-post-listing.png, blog-post.png, blog.diff > > > To make it easier for members of the community to share what's happening in > Apache Cassandra, advertise meetups, and publish other article-style content, > this patch enables simple blogging functionality via the static > cassandra.apache.org site. > > *How does it work?* > The patch uses Jekyll's built-in static blog functionality to add > article-style publishing. It adds no dynamic content, and does not include > commenting or a mechanism for accepting any user-generated content. It makes > the following changes: > – Adds a new layout file for a blog post listing and single-post detail view > (+ supporting CSS). > – Enables pagination of posts via `jekyll-paginate-v2` > – Adds documentation on how to contribute. > – And fixes a
[jira] [Created] (CASSANDRA-14552) Website: Add Static Blogging / Article Publishing to cassandra.apache.org
C. Scott Andreas created CASSANDRA-14552: Summary: Website: Add Static Blogging / Article Publishing to cassandra.apache.org Key: CASSANDRA-14552 URL: https://issues.apache.org/jira/browse/CASSANDRA-14552 Project: Cassandra Issue Type: Improvement Components: Documentation and Website Reporter: C. Scott Andreas Assignee: C. Scott Andreas Attachments: blog-post-listing.png, blog-post.png, blog.diff To make it easier for members of the community to share what's happening in Apache Cassandra, advertise meetups, and publish other article-style content, this patch enables simple blogging functionality via the static cassandra.apache.org site. *How does it work?* The patch uses Jekyll's built-in static blog functionality to add article-style publishing. It adds no dynamic content, and does not include commenting or a mechanism for accepting any user-generated content. It makes the following changes: – Adds a new layout file for a blog post listing and single-post detail view (+ supporting CSS). – Enables pagination of posts via `jekyll-paginate-v2` – Adds documentation on how to contribute. – And fixes a minor documentation issue specifying a Ruby version that conflicts with earlier guidance in the documentation. *How do I write a post?* The patch includes a /_templates folder with an example post to begin. Blog posts are written using Markdown. To write a new post, copy the template into /_posts, rename the file in keeping with the `MM-DD--blog-post-slug.markdown` convention, add the title/date, and begin writing. These pages are generated via the existing build process documented in the README – `make serve` to preview, `make` to publish. *What else should I know?* The aim of this patch is to make it easy to write and publish. The "/blog" link is currently hidden from the top nav and no posts are included in this patch, but this can be enabled once the first article is ready. *What's it look like?* Screenshots of the generated post list view and single-post view attached. !blog-post-listing.png! !blog-post.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
