Re: Is there a blog for commons?
On Fri, 19 Apr 2024 at 16:11, Gary Gregory wrote: > > It sounds to me like the Apache wide news blog is the best place or the > site. Or both: - ASF news could have a general blog entry that draws attention to the feature - Commons site would be used for more specific entries. Posting on the ASF news blog alone is unlikely to be noticed by existing Commons users. > A new blog no one's seen before would not achieve that. Once we > publish it, it's up to us to promote it our socials. > > Gary > > On Fri, Apr 19, 2024, 10:32 AM Claude Warren wrote: > > > I was really looking for a way to reach out to developers that do not know > > that there is a Bloom filter implementation and may not know how they could > > use one. Once someone knows they'll look in the project documentation and > > or javadoc (so I have no issue putting the info there as well). > > > > On Fri, Apr 19, 2024 at 2:43 PM Gary Gregory > > wrote: > > > > > How about putting this in the Javadoc at the package level in > > > package-info.java? > > > > > > Closer to the code is more likely to be maintained than out in the wild > > on > > > a blog. > > > > > > Gary > > > > > > On Fri, Apr 19, 2024, 8:29 AM Gilles Sadowski > > > wrote: > > > > > > > Le ven. 19 avr. 2024 à 13:05, Gary Gregory a > > > > écrit : > > > > > > > > > > I think there are three places today this type of information can > > live > > > > > within Apache: > > > > > > > > > > - the component website (which we can publish whenever we want) > > > > > - the project wiki (which automatically is live) > > > > > - https://news.apache.org/ (not sure how one posts there) > > > > > > > > I beg to differ. > > > > From what I understand, this would be much more useful in a > > > > documentation section of the component (as a practical way to > > > > learn how to use non-trivial functionality implemented there). > > > > > > > > [If the primary purpose is personal advertisement, there is no > > > > real point discussing it on the Commons "dev" ML.] > > > > > > > > Regards, > > > > Gilles > > > > > > > > > > > > > > [...] > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > > > > > > -- > > LinkedIn: http://www.linkedin.com/in/claudewarren > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: Is there a blog for commons?
It sounds to me like the Apache wide news blog is the best place or the site. A new blog no one's seen before would not achieve that. Once we publish it, it's up to us to promote it our socials. Gary On Fri, Apr 19, 2024, 10:32 AM Claude Warren wrote: > I was really looking for a way to reach out to developers that do not know > that there is a Bloom filter implementation and may not know how they could > use one. Once someone knows they'll look in the project documentation and > or javadoc (so I have no issue putting the info there as well). > > On Fri, Apr 19, 2024 at 2:43 PM Gary Gregory > wrote: > > > How about putting this in the Javadoc at the package level in > > package-info.java? > > > > Closer to the code is more likely to be maintained than out in the wild > on > > a blog. > > > > Gary > > > > On Fri, Apr 19, 2024, 8:29 AM Gilles Sadowski > > wrote: > > > > > Le ven. 19 avr. 2024 à 13:05, Gary Gregory a > > > écrit : > > > > > > > > I think there are three places today this type of information can > live > > > > within Apache: > > > > > > > > - the component website (which we can publish whenever we want) > > > > - the project wiki (which automatically is live) > > > > - https://news.apache.org/ (not sure how one posts there) > > > > > > I beg to differ. > > > From what I understand, this would be much more useful in a > > > documentation section of the component (as a practical way to > > > learn how to use non-trivial functionality implemented there). > > > > > > [If the primary purpose is personal advertisement, there is no > > > real point discussing it on the Commons "dev" ML.] > > > > > > Regards, > > > Gilles > > > > > > > > > > > [...] > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > -- > LinkedIn: http://www.linkedin.com/in/claudewarren >
Re: Is there a blog for commons?
I was really looking for a way to reach out to developers that do not know that there is a Bloom filter implementation and may not know how they could use one. Once someone knows they'll look in the project documentation and or javadoc (so I have no issue putting the info there as well). On Fri, Apr 19, 2024 at 2:43 PM Gary Gregory wrote: > How about putting this in the Javadoc at the package level in > package-info.java? > > Closer to the code is more likely to be maintained than out in the wild on > a blog. > > Gary > > On Fri, Apr 19, 2024, 8:29 AM Gilles Sadowski > wrote: > > > Le ven. 19 avr. 2024 à 13:05, Gary Gregory a > > écrit : > > > > > > I think there are three places today this type of information can live > > > within Apache: > > > > > > - the component website (which we can publish whenever we want) > > > - the project wiki (which automatically is live) > > > - https://news.apache.org/ (not sure how one posts there) > > > > I beg to differ. > > From what I understand, this would be much more useful in a > > documentation section of the component (as a practical way to > > learn how to use non-trivial functionality implemented there). > > > > [If the primary purpose is personal advertisement, there is no > > real point discussing it on the Commons "dev" ML.] > > > > Regards, > > Gilles > > > > > > > > [...] > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > -- LinkedIn: http://www.linkedin.com/in/claudewarren
Re: [LAZY][VOTE] Release Apache Commons Release Plugin 1.8.2 based on RC1
My +1 Gary On Mon, Apr 15, 2024 at 9:05 PM Gary Gregory wrote: > > We have fixed a few bugs and added enhancements since Apache Commons > Release Plugin 1.8.1 was released, so I would like to release Apache > Commons Release Plugin 1.8.2. > > Apache Commons Release Plugin 1.8.2 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.2-RC1 > (svn revision 68552) > > The Git tag commons-release-plugin-1.8.2-RC1 commit for this RC is > d5fa1ff2f5b4ad5adb3acd39f4e7360f59704205 which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-release-plugin.git;a=commit;h=d5fa1ff2f5b4ad5adb3acd39f4e7360f59704205 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-release-plugin.git > --branch commons-release-plugin-1.8.2-RC1 > commons-release-plugin-1.8.2-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1721/org/apache/commons/commons-release-plugin/1.8.2/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Tue Apr 16 00:55:51 UTC 2024 > commons-release-plugin-1.8.2-bin.zip=2a547ef3c72405f297b837b87f975eb5463b6fe017ea72fc72fecd245ca0533ad211231350cd1b70c30ce9317c597838cd9146913c94f668b11f783feea9a970 > commons-release-plugin-1.8.2-sources.jar=cc49b6cc1b1993da0b3b1c9394b10708cf07634ddd455f710e82f5d3a1256ce399ef320184d0116a092cee586fa633afeff4931768703a0467cfe5dc47dd8ac8 > commons-release-plugin-1.8.2-bin.tar.gz=9da41fdb453c9027a2abc321d547033ea893952dccec172d959b8e8db884e221ae5bdbf5a150c5329dca3bb6e015401639c69f2d2f2815ba416c75189a55 > commons-release-plugin-1.8.2-javadoc.jar=19a440a12c26fb4261f600a0ebee0dc2463251fcdb2c82b9d7501a09597faa5830a6e9323268f0af6707216b91d26b10ea529553821ab0627b0a1dcf08d25914 > commons-release-plugin-1.8.2-test-sources.jar=3fe71f4a31f66d9f391741d3dcfd3582938d7fd22cb66e3f2c82b00d8fae7b8101a5eb757f06d46281cce71513f64508491999f8e25fba4df0a9971f2b0e6858 > commons-release-plugin-1.8.2-bom.xml=aac5c147a1049ce0eb8bdc20d3f51f3ce9c7e87b35b2d500da3c0c955dbff186a23e4600411b18721b146d804d7909c55ad2b8eb5ab82166410d1540fdcb0b65 > commons-release-plugin-1.8.2-bom.json=406a4a32a784142de77e81579df6cf030a1deca837d44c779d498134d12872233533146ef6bdd6a0ea5984b7a307e7d9cebcf63781db814713ce7336a2d94727 > commons-release-plugin-1.8.2-tests.jar=19ebc95faeacbb253058762d9b6edf11b9c22f9825557d00cc9d871c2ae86beafb93f0106ec9f59830a3eacc1d069f2611dd64324c43949770b427976afe49c7 > org.apache.commons_commons-release-plugin-1.8.2.spdx.json=7d1262c9f11c161bba7f09abee7345a74b37f65cb00e1ce5fd13f6eff6f977d5d1c8982f0cca65dbeb1ba7a69eb77941b672b90f2fc2d8908b15ae3bb67b9b74 > commons-release-plugin-1.8.2-src.tar.gz=0579a023f926da53b5d2f273676c1bdd1cff1cf1a9f4e45bfc78370cb3111d91c73216251b4e1b79511e4eb41cc867d1ac80a2c2f77a0a60dcc687fc5edc904f > commons-release-plugin-1.8.2-src.zip=7a9c27460158ef13a1ff2723a5c2fea7f0a825031f0513c14f83c154ea36437545c812729cd7af8b361b66f95905e55434164cb3ca858bdebee6600d331d0028 > > I have tested this with 'mvn' and 'mvn -V -Prelease -Ptest-deploy -P > jacoco -P japicmp clean package site deploy' using: > > penjdk version "17.0.10" 2024-01-16 > OpenJDK Runtime Environment Homebrew (build 17.0.10+0) > OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing) > > Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) > Maven home: /usr/local/Cellar/maven/3.9.6/libexec > Java version: 17.0.10, vendor: Homebrew, runtime: > /usr/local/Cellar/openjdk@17/17.0.10/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "14.4.1", arch: "x86_64", family: "mac" > > Darwin 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:05 > PDT 2024; root:xnu-10063.101.17~1/RELEASE_X86_64 x86_64 > > Details of changes since 1.8.1 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.2-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.2-RC1/site/changes-report.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.2-RC1/site/index.html > (note some *relative* links are broken and the 1.8.2 directories > are not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 1.8.1): > > https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.2-RC1/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.2-RC1/site/rat-report.html > > KEYS: > https://downloads.apache.org/commons/KEYS > > Please review the release candidate and vote. > This vote will close no sooner than 72 hours from now. > > [ ] +1 Release these artifacts > [ ] +0 OK, but... > [ ] -0 OK, but really should fix... > [ ] -1 I oppose this release because... > > Thank you, > > Gary Gregory, > Release Manager (using key 86fdc7e2a11262cb) > > For
[RESULT][LAZY][VOTE] Release Apache Commons Release Plugin 1.8.2 based on RC1
This lazy voting thread passes with the following binding +1 votes: - Gary Gregory (ggregory) Gary On Fri, Apr 19, 2024 at 10:29 AM Gary Gregory wrote: > > My +1 > > Gary > > On Mon, Apr 15, 2024 at 9:05 PM Gary Gregory wrote: > > > > We have fixed a few bugs and added enhancements since Apache Commons > > Release Plugin 1.8.1 was released, so I would like to release Apache > > Commons Release Plugin 1.8.2. > > > > Apache Commons Release Plugin 1.8.2 RC1 is available for review here: > > https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.2-RC1 > > (svn revision 68552) > > > > The Git tag commons-release-plugin-1.8.2-RC1 commit for this RC is > > d5fa1ff2f5b4ad5adb3acd39f4e7360f59704205 which you can browse here: > > > > https://gitbox.apache.org/repos/asf?p=commons-release-plugin.git;a=commit;h=d5fa1ff2f5b4ad5adb3acd39f4e7360f59704205 > > You may checkout this tag using: > > git clone https://gitbox.apache.org/repos/asf/commons-release-plugin.git > > --branch commons-release-plugin-1.8.2-RC1 > > commons-release-plugin-1.8.2-RC1 > > > > Maven artifacts are here: > > > > https://repository.apache.org/content/repositories/orgapachecommons-1721/org/apache/commons/commons-release-plugin/1.8.2/ > > > > These are the artifacts and their hashes: > > > > #Release SHA-512s > > #Tue Apr 16 00:55:51 UTC 2024 > > commons-release-plugin-1.8.2-bin.zip=2a547ef3c72405f297b837b87f975eb5463b6fe017ea72fc72fecd245ca0533ad211231350cd1b70c30ce9317c597838cd9146913c94f668b11f783feea9a970 > > commons-release-plugin-1.8.2-sources.jar=cc49b6cc1b1993da0b3b1c9394b10708cf07634ddd455f710e82f5d3a1256ce399ef320184d0116a092cee586fa633afeff4931768703a0467cfe5dc47dd8ac8 > > commons-release-plugin-1.8.2-bin.tar.gz=9da41fdb453c9027a2abc321d547033ea893952dccec172d959b8e8db884e221ae5bdbf5a150c5329dca3bb6e015401639c69f2d2f2815ba416c75189a55 > > commons-release-plugin-1.8.2-javadoc.jar=19a440a12c26fb4261f600a0ebee0dc2463251fcdb2c82b9d7501a09597faa5830a6e9323268f0af6707216b91d26b10ea529553821ab0627b0a1dcf08d25914 > > commons-release-plugin-1.8.2-test-sources.jar=3fe71f4a31f66d9f391741d3dcfd3582938d7fd22cb66e3f2c82b00d8fae7b8101a5eb757f06d46281cce71513f64508491999f8e25fba4df0a9971f2b0e6858 > > commons-release-plugin-1.8.2-bom.xml=aac5c147a1049ce0eb8bdc20d3f51f3ce9c7e87b35b2d500da3c0c955dbff186a23e4600411b18721b146d804d7909c55ad2b8eb5ab82166410d1540fdcb0b65 > > commons-release-plugin-1.8.2-bom.json=406a4a32a784142de77e81579df6cf030a1deca837d44c779d498134d12872233533146ef6bdd6a0ea5984b7a307e7d9cebcf63781db814713ce7336a2d94727 > > commons-release-plugin-1.8.2-tests.jar=19ebc95faeacbb253058762d9b6edf11b9c22f9825557d00cc9d871c2ae86beafb93f0106ec9f59830a3eacc1d069f2611dd64324c43949770b427976afe49c7 > > org.apache.commons_commons-release-plugin-1.8.2.spdx.json=7d1262c9f11c161bba7f09abee7345a74b37f65cb00e1ce5fd13f6eff6f977d5d1c8982f0cca65dbeb1ba7a69eb77941b672b90f2fc2d8908b15ae3bb67b9b74 > > commons-release-plugin-1.8.2-src.tar.gz=0579a023f926da53b5d2f273676c1bdd1cff1cf1a9f4e45bfc78370cb3111d91c73216251b4e1b79511e4eb41cc867d1ac80a2c2f77a0a60dcc687fc5edc904f > > commons-release-plugin-1.8.2-src.zip=7a9c27460158ef13a1ff2723a5c2fea7f0a825031f0513c14f83c154ea36437545c812729cd7af8b361b66f95905e55434164cb3ca858bdebee6600d331d0028 > > > > I have tested this with 'mvn' and 'mvn -V -Prelease -Ptest-deploy -P > > jacoco -P japicmp clean package site deploy' using: > > > > penjdk version "17.0.10" 2024-01-16 > > OpenJDK Runtime Environment Homebrew (build 17.0.10+0) > > OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing) > > > > Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) > > Maven home: /usr/local/Cellar/maven/3.9.6/libexec > > Java version: 17.0.10, vendor: Homebrew, runtime: > > /usr/local/Cellar/openjdk@17/17.0.10/libexec/openjdk.jdk/Contents/Home > > Default locale: en_US, platform encoding: UTF-8 > > OS name: "mac os x", version: "14.4.1", arch: "x86_64", family: "mac" > > > > Darwin 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:05 > > PDT 2024; root:xnu-10063.101.17~1/RELEASE_X86_64 x86_64 > > > > Details of changes since 1.8.1 are in the release notes: > > > > https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.2-RC1/RELEASE-NOTES.txt > > > > https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.2-RC1/site/changes-report.html > > > > Site: > > > > https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.2-RC1/site/index.html > > (note some *relative* links are broken and the 1.8.2 directories > > are not yet created - these will be OK once the site is deployed.) > > > > JApiCmp Report (compared to 1.8.1): > > > > https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.2-RC1/site/japicmp.html > > > > RAT Report: > > > > https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.2-RC1/site/rat-report.html > > > > KEYS: > > https://downloads.apache.org/commons/KEYS > > > > Please review
Re: Is there a blog for commons?
How about putting this in the Javadoc at the package level in package-info.java? Closer to the code is more likely to be maintained than out in the wild on a blog. Gary On Fri, Apr 19, 2024, 8:29 AM Gilles Sadowski wrote: > Le ven. 19 avr. 2024 à 13:05, Gary Gregory a > écrit : > > > > I think there are three places today this type of information can live > > within Apache: > > > > - the component website (which we can publish whenever we want) > > - the project wiki (which automatically is live) > > - https://news.apache.org/ (not sure how one posts there) > > I beg to differ. > From what I understand, this would be much more useful in a > documentation section of the component (as a practical way to > learn how to use non-trivial functionality implemented there). > > [If the primary purpose is personal advertisement, there is no > real point discussing it on the Commons "dev" ML.] > > Regards, > Gilles > > > > > [...] > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
Re: Is there a blog for commons?
Le ven. 19 avr. 2024 à 13:05, Gary Gregory a écrit : > > I think there are three places today this type of information can live > within Apache: > > - the component website (which we can publish whenever we want) > - the project wiki (which automatically is live) > - https://news.apache.org/ (not sure how one posts there) I beg to differ. >From what I understand, this would be much more useful in a documentation section of the component (as a practical way to learn how to use non-trivial functionality implemented there). [If the primary purpose is personal advertisement, there is no real point discussing it on the Commons "dev" ML.] Regards, Gilles > > [...] - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: Is there a blog for commons?
Hi Bruno, On Fri, 19 Apr 2024 at 13:30, Bruno Kinoshita wrote: > Maybe an option would be to just have it under > https://commons.apache.org/blog/, as part of the project website in Git, > published with the site manually/ASF CRM/etc? I think that way INFRA would > not have to be involved? The Logging Services blog[1] uses Jekyll under the hood. This is already supported by INFRA through an `.asf.yaml` configuration option[2]. Piotr [1] https://logging.apache.org/blog/ [2] https://github.com/apache/infrastructure-asfyaml/blob/main/README.md#jekyll_cms - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: Is there a blog for commons?
> > Is there another > Apache project that has its own blog but does not fit in the list above? - https://openoffice.apache.org/blogpage.html - https://arrow.apache.org/blog/ - https://spark.apache.org/news/ (mostly about releases though) - https://airflow.apache.org/blog/ - https://kafka.apache.org/blog - ... Maybe an option would be to just have it under https://commons.apache.org/blog/, as part of the project website in Git, published with the site manually/ASF CRM/etc? I think that way INFRA would not have to be involved? Cheers On Fri, 19 Apr 2024 at 13:05, Gary Gregory wrote: > I think there are three places today this type of information can live > within Apache: > > - the component website (which we can publish whenever we want) > - the project wiki (which automatically is live) > - https://news.apache.org/ (not sure how one posts there) > > A new blog (whatever that means using whatever stack) would likely require > involvement from infra which is already overwhelmed. Is there another > Apache project that has its own blog but does not fit in the list above? > > Gary > > On Fri, Apr 19, 2024, 2:42 AM Claude Warren wrote: > > > I have what is currently a series of 4 blogs that introduce the new Bloom > > filter implementations and framework in Commons Collections. I have a > > couple more in mind, they discuss what Bloom filters are and how the > > Commons Collections implements them, provides extension points, and how > to > > implement some exotic flavors. In fact I have an implementation for a > > Kafka PID tracking problem (KIP-936) that uses layered Bloom filters to > > track PIDs in a time window while handling bursty traffic and not > exceeding > > the desired false positive rate. > > > > So these are rather technical posts, they could be transformed into pages > > in documentation, but what I really want to do is get attention on the > tool > > from developers of other projects, to let them know the tools exist. I > > think that if the ASF had a technical blog we could be promoting our > > projects to the wider development world. I can think of other projects > > that could have rather interesting blogs. For example, a discussion of > > Cassandra's new Accord consensus protocol could help other ASF projects > > working on consensus issues. Kafka too has a consensus protocol they are > > working on. > > > > Is there any interest in a technical blog that focus on the solutions to > > technical problems within a project rather than the higher level > technical > > problems solved by the project. So not that Cassandra has a solution to > a > > distributed database problem, but Cassandra solved the consensus problem > > this way; not Kafka solves the data streaming problem, but Kafka solved > the > > consensus problem this way. (OK, too much consensus, but you see what I > > mean). > > > > Claude > > > > > > > > On Wed, Apr 17, 2024 at 8:07 PM Gary Gregory > > wrote: > > > > > Well, we already have https://news.apache.org/ > > > > > > Gary > > > > > > On Wed, Apr 17, 2024, 1:50 PM Elric V wrote: > > > > > > > On 16/04/2024 13:08, Gary Gregory wrote: > > > > > There is an Apache wide blog here: > > > > > https://news.apache.org/ > > > > > > > > There used to be a planet.apache.org which aggregated > > committer/project > > > > blogs, but that seems to be broken. > > > > > > > > Would there be any interets in an aggregated ASF-project wide blog? > > > > Where contributors from all projects could submit posts? Would be a > > > > great way to keep up to do date, as well as learn about other ASF > > > projects. > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > > > > > > -- > > LinkedIn: http://www.linkedin.com/in/claudewarren > > >
Re: Is there a blog for commons?
I think there are three places today this type of information can live within Apache: - the component website (which we can publish whenever we want) - the project wiki (which automatically is live) - https://news.apache.org/ (not sure how one posts there) A new blog (whatever that means using whatever stack) would likely require involvement from infra which is already overwhelmed. Is there another Apache project that has its own blog but does not fit in the list above? Gary On Fri, Apr 19, 2024, 2:42 AM Claude Warren wrote: > I have what is currently a series of 4 blogs that introduce the new Bloom > filter implementations and framework in Commons Collections. I have a > couple more in mind, they discuss what Bloom filters are and how the > Commons Collections implements them, provides extension points, and how to > implement some exotic flavors. In fact I have an implementation for a > Kafka PID tracking problem (KIP-936) that uses layered Bloom filters to > track PIDs in a time window while handling bursty traffic and not exceeding > the desired false positive rate. > > So these are rather technical posts, they could be transformed into pages > in documentation, but what I really want to do is get attention on the tool > from developers of other projects, to let them know the tools exist. I > think that if the ASF had a technical blog we could be promoting our > projects to the wider development world. I can think of other projects > that could have rather interesting blogs. For example, a discussion of > Cassandra's new Accord consensus protocol could help other ASF projects > working on consensus issues. Kafka too has a consensus protocol they are > working on. > > Is there any interest in a technical blog that focus on the solutions to > technical problems within a project rather than the higher level technical > problems solved by the project. So not that Cassandra has a solution to a > distributed database problem, but Cassandra solved the consensus problem > this way; not Kafka solves the data streaming problem, but Kafka solved the > consensus problem this way. (OK, too much consensus, but you see what I > mean). > > Claude > > > > On Wed, Apr 17, 2024 at 8:07 PM Gary Gregory > wrote: > > > Well, we already have https://news.apache.org/ > > > > Gary > > > > On Wed, Apr 17, 2024, 1:50 PM Elric V wrote: > > > > > On 16/04/2024 13:08, Gary Gregory wrote: > > > > There is an Apache wide blog here: > > > > https://news.apache.org/ > > > > > > There used to be a planet.apache.org which aggregated > committer/project > > > blogs, but that seems to be broken. > > > > > > Would there be any interets in an aggregated ASF-project wide blog? > > > Where contributors from all projects could submit posts? Would be a > > > great way to keep up to do date, as well as learn about other ASF > > projects. > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > -- > LinkedIn: http://www.linkedin.com/in/claudewarren >
Re: [Collections-BloomFilter][Discuss] missing functionality?
On Fri, 19 Apr 2024 at 08:26, Claude Warren wrote:
> While the Deque makes clear the idea of enqueueing and dequeueing the
> layers it does not have the method to natively traverse and extract entries
> from the middle of the queue. Nor would I expect it to. So I think the
> Deque does not accurately reflect how the collection of Bloom filters is
> utilized.
>
You can traverse and remove entries with the Iterator of the Deque:
Deque d = new LinkedList<>();
d.addAll(Arrays.asList(1, 2, 3, 4, 5));
for (Iterator it = d.iterator(); it.hasNext();) {
int i = it.next();
if (i == 3) {
it.remove();
}
}
System.out.println(d);
prints:
[1, 2, 4, 5]
So it is easy to iterate the layers and remove them in Order(1) time (per
removal).
Alex
>
> On Wed, Apr 17, 2024 at 2:17 PM Alex Herbert
> wrote:
>
> > Looks good to me.
> >
> > Any opinions on changing the LayerManager to keep the layers in a Deque
> > rather than a LinkedList. I think it would only require a change to the
> > following method:
> >
> > public final BloomFilter get(int depth)
> >
> > Performance will be the same as the Deque can be a LinkedList. This is
> more
> > about how any custom downstream code is currently using the collection of
> > layers.
> >
> > Alex
>
>
Re: [Collections-BloomFilter][Discuss] missing functionality?
While the Deque makes clear the idea of enqueueing and dequeueing the
layers it does not have the method to natively traverse and extract entries
from the middle of the queue. Nor would I expect it to. So I think the
Deque does not accurately reflect how the collection of Bloom filters is
utilized.
On Wed, Apr 17, 2024 at 2:17 PM Alex Herbert
wrote:
> Looks good to me.
>
> Any opinions on changing the LayerManager to keep the layers in a Deque
> rather than a LinkedList. I think it would only require a change to the
> following method:
>
> public final BloomFilter get(int depth)
>
> Performance will be the same as the Deque can be a LinkedList. This is more
> about how any custom downstream code is currently using the collection of
> layers.
>
> Alex
>
> On Wed, 17 Apr 2024 at 10:00, Claude Warren wrote:
>
> > I have an open pull request to fix this problem. I could use another
> > review: https://github.com/apache/commons-collections/pull/476
> >
> >
> > On Tue, Apr 9, 2024 at 11:29 AM Claude Warren wrote:
> >
> > > Alex,
> > >
> > > I like your solution. To answer your question. We create a BloomFilter
> > > that has a timestamp associated with it. When the timestamp is greater
> > > than System.currentTimeMillis() the filter is removed. The custom
> > cleanup
> > > calls Cleanup.removeEmptyTarget().andThen()
> > >
> > > I think that creating a cleanup() or clean() method on the
> > > LayeredBloomFilter is the appropriate solution and that it should call
> > > cleanup() on the LayerManager. (so 2 new methods, one exposed).
> > >
> > > The next() method is used when external circumstances dictate that a
> new
> > > layer should be created. I think a StableBloomFilter I implemented
> > > required it, but I do not have the code to hand at the moment.
> > >
> > > Claude
> > >
> > >
> > > On Tue, Apr 9, 2024 at 10:38 AM Alex Herbert >
> > > wrote:
> > >
> > >> Hi Claude,
> > >>
> > >> Q. What is your current clean-up filter, i.e.
> > >> the Consumer>? I assume you are using a custom
> > >> one.
> > >>
> > >> The current collections code only has 2 functional implementations.
> One
> > >> will remove the newest filter if it is empty, one will remove the
> oldest
> > >> filters until the size is below a limit. Since neither of those will
> > >> iterate the list and purge stale objects then I assume you are using a
> > >> custom clean-up filter. So you had to have created the layer manager
> > with
> > >> your custom filter. Assuming this then there are at least two
> solutions
> > >> for
> > >> the current code:
> > >>
> > >> 1. The current implementation always calls the clean-up filter with
> the
> > >> same LinkedList since it is final. So you can capture the list and do
> > what
> > >> you want with it:
> > >>
> > >> @SuppressWarnings("rawtypes")
> > >> LinkedList[] captured = new LinkedList[1];
> > >> Consumer> cleanup = list -> {
> > >> captured[0] = list;
> > >> // ... do clean-up
> > >> };
> > >>
> > >> // Once you have captured the list, you can clean it when you
> > >> want:
> > >> // unchecked conversion
> > >> cleanup.accept(captured[0]);
> > >>
> > >> Obviously this is not ideal as you have to manage the captured list to
> > >> call
> > >> cleanup. But it delivers exactly what you require in terms of being
> able
> > >> to
> > >> call cleanup at any time.
> > >>
> > >> 2. The call to next() will clean the layers but also add a new layer.
> So
> > >> your custom clean method could clean stale objects and also any empty
> > >> filters not at the end of the list. This will avoid building up lots
> of
> > >> empty filters when you frequently trigger next() to purge stale
> filters.
> > >> You can call next() directly on the LayeredBloomFilter. I do not know
> > what
> > >> extend check you are using so there is some management to be done with
> > the
> > >> other settings of the LayerManager to avoid removing any functional
> > layers
> > >> which are currently empty.
> > >>
> > >> --
> > >>
> > >> As to exposing the LayerManager and adding a clean() method to the
> > >> LayerManager, I think this is not in keeping with the current design.
> > The
> > >> LayerManager is used during construction and then never used again. So
> > >> functionality to act on the layers is public through the
> > >> LayeredBloomFilter
> > >> (e.g. calling next()). So perhaps the change to the API should be to
> > add a
> > >> cleanup() method to LayeredBloomFilter. This does the same as next(),
> > but
> > >> does not add a new layer.
> > >>
> > >> I cannot recall the use case for next() in the LayeredBloomFilter.
> Would
> > >> the addition of cleanup() make the next() method redundant?
> > >>
> > >> --
> > >>
> > >> Note: The typing against LinkedList could be updated to
> java.util.Deque.
> > >> The only issue with this is the method:
> > >> public final BloomFilter get(int depth)
> > >>
> > >> This is not supported by the
Re: Is there a blog for commons?
I have what is currently a series of 4 blogs that introduce the new Bloom filter implementations and framework in Commons Collections. I have a couple more in mind, they discuss what Bloom filters are and how the Commons Collections implements them, provides extension points, and how to implement some exotic flavors. In fact I have an implementation for a Kafka PID tracking problem (KIP-936) that uses layered Bloom filters to track PIDs in a time window while handling bursty traffic and not exceeding the desired false positive rate. So these are rather technical posts, they could be transformed into pages in documentation, but what I really want to do is get attention on the tool from developers of other projects, to let them know the tools exist. I think that if the ASF had a technical blog we could be promoting our projects to the wider development world. I can think of other projects that could have rather interesting blogs. For example, a discussion of Cassandra's new Accord consensus protocol could help other ASF projects working on consensus issues. Kafka too has a consensus protocol they are working on. Is there any interest in a technical blog that focus on the solutions to technical problems within a project rather than the higher level technical problems solved by the project. So not that Cassandra has a solution to a distributed database problem, but Cassandra solved the consensus problem this way; not Kafka solves the data streaming problem, but Kafka solved the consensus problem this way. (OK, too much consensus, but you see what I mean). Claude On Wed, Apr 17, 2024 at 8:07 PM Gary Gregory wrote: > Well, we already have https://news.apache.org/ > > Gary > > On Wed, Apr 17, 2024, 1:50 PM Elric V wrote: > > > On 16/04/2024 13:08, Gary Gregory wrote: > > > There is an Apache wide blog here: > > > https://news.apache.org/ > > > > There used to be a planet.apache.org which aggregated committer/project > > blogs, but that seems to be broken. > > > > Would there be any interets in an aggregated ASF-project wide blog? > > Where contributors from all projects could submit posts? Would be a > > great way to keep up to do date, as well as learn about other ASF > projects. > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > -- LinkedIn: http://www.linkedin.com/in/claudewarren
