datasketches 0.3.2 → 0.4.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e0c6cc871dc7c8726b31146fe287dd337e6aa5c1c70a234d2ad77b5bed74aca2
-  data.tar.gz: c5e89d9d28069aec80863fa6e1da339457dcc04f938d3b3506a3dfbb66899eee
+  metadata.gz: deea49b435964ffbdc1d453f513af8b694a5b81bce8777d48fe3988d7476a538
+  data.tar.gz: e59c962f8fe1c0b5175a4ef0b076d8e19756de874d0ec300dd91c08f829f73c6
 SHA512:
-  metadata.gz: 36459e338671867ae63de590a6807f801891a9821336178e64bca0d9b1615c263aac5160b4f1cf74796c5756bfee4a36335585db6354f0d2e7a77765236e9730
-  data.tar.gz: dff58e6888788ce030484c6027f9a9bfee42b0315a18f6a2b02695336be482a7a255576efe0b128b2dbee99f50fd5184c788dbe799815a5a8839143d2b3642f3
+  metadata.gz: 542d7d5976324498d58dc5aeebc66bb9c0fafbe32544a44f0618cb78f2d5957dae947325128075e4c963811adcfa8566acffa280a9c82c23fdbd787d327410be
+  data.tar.gz: c052d36c667fa9b9638f682e3b71969f1f74009db50a50bf38682adb13122ec1ab6829613ce626233fe06cf787c6d2c473c3359ca183dc565ac1dc3eefa637b9

data/CHANGELOG.md

@@ -1,3 +1,9 @@
+## 0.4.0 (2023-11-13)
+
+- Updated DataSketches to 5.0.0
+- Removed `quantiles` method from KLL sketches
+- Dropped support for Ruby < 3
+
 ## 0.3.2 (2023-05-03)
 
 - Updated DataSketches to 4.1.0

data/NOTICE

@@ -1,5 +1,5 @@
 Apache DataSketches C++ and Python
-Copyright 2022 The Apache Software Foundation
+Copyright 2023 The Apache Software Foundation
 
 Copyright 2015-2018 Yahoo Inc.
 Copyright 2019-2020 Verizon Media

data/README.md

@@ -235,8 +235,6 @@ Get quantiles
 
 ```ruby
 sketch.quantile(0.5)
-sketch.quantiles([0.25, 0.5, 0.75])
-sketch.quantiles(3)
 ```
 
 Get the minimum and maximum values from the stream

data/ext/datasketches/cpc_wrapper.cpp

@@ -8,14 +8,14 @@
 using datasketches::cpc_sketch;
 using datasketches::cpc_union;
 
-using datasketches::CPC_DEFAULT_LG_K;
+using datasketches::cpc_constants::DEFAULT_LG_K;
 using datasketches::DEFAULT_SEED;
 
 using Rice::Arg;
 
 void init_cpc(Rice::Module& m) {
   Rice::define_class_under<cpc_sketch>(m, "CpcSketch")
-    .define_constructor(Rice::Constructor<cpc_sketch, uint8_t, uint64_t>(), Rice::Arg("lg_k")=CPC_DEFAULT_LG_K, Rice::Arg("seed")=DEFAULT_SEED)
+    .define_constructor(Rice::Constructor<cpc_sketch, uint8_t, uint64_t>(), Rice::Arg("lg_k")=DEFAULT_LG_K, Rice::Arg("seed")=DEFAULT_SEED)
     .define_method("lg_k", &cpc_sketch::get_lg_k)
     .define_method("empty?", &cpc_sketch::is_empty)
     .define_method("lower_bound", &cpc_sketch::get_lower_bound)

data/ext/datasketches/kll_wrapper.cpp

@@ -38,16 +38,6 @@ void bind_kll_sketch(Rice::Module& m, const char* name) {
       [](kll_sketch<T>& self, double rank, bool inclusive) {
         return self.get_quantile(rank, inclusive);
       }, Rice::Arg("rank"), Rice::Arg("inclusive")=false)
-    .define_method(
-      "quantiles",
-      [](kll_sketch<T>& self, Rice::Object obj, bool inclusive) {
-        if (obj.is_a(rb_cArray)) {
-          auto ranks = Rice::detail::From_Ruby<std::vector<double>>().convert(obj);
-          return self.get_quantiles(&ranks[0], ranks.size(), inclusive);
-        } else {
-          return self.get_quantiles(Rice::detail::From_Ruby<size_t>().convert(obj), inclusive);
-        }
-      }, Rice::Arg("obj"), Rice::Arg("inclusive")=false)
     .define_method(
       "rank",
       [](kll_sketch<T>& self, const T item, bool inclusive) {

data/lib/datasketches/version.rb

@@ -1,3 +1,3 @@
 module DataSketches
-  VERSION = "0.3.2"
+  VERSION = "0.4.0"
 end

data/lib/datasketches.rb

@@ -2,7 +2,7 @@
 require "datasketches/ext"
 
 # modules
-require "datasketches/version"
+require_relative "datasketches/version"
 
 module DataSketches
   class Error < StandardError; end

data/vendor/datasketches-cpp/CMakeLists.txt

@@ -70,6 +70,7 @@ set(CMAKE_CXX_EXTENSIONS OFF)
 # Enable testing
 option(BUILD_TESTS "Build unit tests" ON)
 if (BUILD_TESTS)
+  list(APPEND CMAKE_CTEST_ARGUMENTS "--output-on-failure")
   enable_testing()
 endif()
 

data/vendor/datasketches-cpp/CODE_OF_CONDUCT.md

@@ -0,0 +1,3 @@
+# Code of Conduct
+
+We adhere to the Apache Softare Foundation's [Code of Conduct](https://www.apache.org/foundation/policies/conduct).

data/vendor/datasketches-cpp/CONTRIBUTING.md

@@ -0,0 +1,50 @@
+# Contributing
+
+## How We Communicate
+
+There are many ways that are available for our community to communicate with each other and directly with our developers.  Please review the following for methods that meet your needs.
+
+### [Users Mailing List](https://lists.apache.org/list.html?users@datasketches.apache.org) 
+This is a great place for all users (new and experienced) to ask general questions about the library, its general capabilities, and where to get help and find more information.  This is also a great place to give the developers general feedback about the library. If you like what you see, please give us a [Star (Java)](https://github.com/apache/datasketches-java) and/or [Star (C++/Python)](https://github.com/apache/datasketches-cpp) If you have general suggestions on how we can improve we would like to hear from you.  All of our developers follow this list and all sincere questions and comments will get a response.
+    
+* To subscribe send an empty email to [users-subscribe@datasketches.apache.org](mailto:users-subscribe@datasketches.apache.org).
+* To unsubscribe send an empty email to [users-unsubscribe@datasketches.apache.org](mailto:users-unsubscribe@datasketches.apache.org).
+  
+### [Developers Mailing List](https://lists.apache.org/list.html?dev@datasketches.apache.org)
+This is where the developers, committers, and contributors congregate to discuss, vote and establish priorities on addressing issues and opportunities with the library. The issues discussed tend to apply across all the different components of the library (see below).
+    
+* To subscribe send an empty email to [dev-subscribe@datasketches.apache.org](mailto:dev-subscribe@datasketches.apache.org).
+* To unsubscribe send an empty email to [dev-unsubscribe@datasketches.apache.org](mailto:dev-unsubscribe@datasketches.apache.org).
+
+### Slack
+Chat with users and developers on Slack in _the-asf.slack.com_ workspace. 
+
+* Anyone with an _apache.org_ email account can freely join via [ASF Slack Signup](https://the-asf.slack.com/signup).
+* Otherwise, please send an email to our developers mail list above and we will send you an invite to join our slack channel. Join the _#datasketches_ channel when you receive notification.
+
+### Bugs and Issues
+If you have a problem or issue with any aspect of the performance, accuracy or documentation in our library please file an issue with the relevant [Component](https://datasketches.apache.org/docs/Architecture/Components.html) GitHub site.
+
+
+## Contributing
+
+We are always open to contributions from our community.  Contributions can be of many forms: documentation, testing, science as well as bug fixes, code enhancements, code reviews, feature suggestions, usability feedback, etc. Contributions usually take the form of a Pull Request (PR), but if you wish to contribute and not sure how, please contact us on our <dev@datasketches.apache.org> list.  
+
+We are also open to the submission of entirely new sketch algorithms.  If you have a sketch algorithm (or a significant enhancement of our current algorithms), please read our [Sketch Criteria](https://datasketches.apache.org/docs/Architecture/SketchCriteria.html) and contact us on our <dev@datasketches.apache.org> list.
+
+## [Our Component Repositories](https://datasketches.apache.org/docs/Architecture/Components.html)
+
+### What to work on
+* Our library is made up of components that are partitioned into GitHub repositories. If you have a specific issue or bug report that impacts only one of these components please open an issue on the respective component. If you are a developer and wish to submit a PR, please choose the appropriate repository. But most important, please contact us on <dev@datasketches.apache.org>
+
+* We have three TODO lists for [Java](https://github.com/apache/datasketches-java/projects/1), [C++](https://github.com/apache/datasketches-cpp/projects/1) and the [Website](https://github.com/apache/datasketches-website/projects/1). Please check these out for potential contribution!
+
+### Getting your proposed changes accepted
+
+Proposed changes to the code or documentation are usually done through GitHub Pull Requests (PRs).
+
+* Simple PRs, such as simple bug fixes, typos, and documentation corrections require one approval vote (+1) from a committer.
+* Major changes to the code such as API or architectural changes or new sketch algorithms must be discussed on <dev@datasketches.apache.org> or on a GitHub issue as these will require additional design and compatibility reviews. These changes must receive at least three (+1) votes from committers. If the author is already a committer, than two additional committers must vote (+1). 
+
+### Becoming a committer
+We welcome anyone who is eager to continue to contribute to the DataSketches mission of providing open source, production quality sketch algorithms and become part of our team.  Please send us a message on <dev@datasketches.apache.org> where we can give you some guidance.  After you have made some successful contributions, the current committers will discuss your candidacy for becoming a committer.  You can also review the [Apache policies on becoming a committer](https://community.apache.org/contributors/index.html) as well as our [New Committer Process](https://datasketches.apache.org/docs/Community/NewCommitterProcess.html) for selecting and inviting a committer to join our project.