You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/09/01 14:53:00 UTC
[jira] [Commented] (METRON-1148) Add SET and MULTISET data
structures to stellar
[ https://issues.apache.org/jira/browse/METRON-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16150664#comment-16150664 ]
ASF GitHub Bot commented on METRON-1148:
----------------------------------------
GitHub user cestella opened a pull request:
https://github.com/apache/metron/pull/728
METRON-1148: Add SET and MULTISET data structures to stellar
## Contributor Comments
With the addition of geohashes, to do analytics like tracking the statistical distribution of the distances of a user's login against the centroid of the user logins across some time, there is a need to be able to store sets (e.g. sets of geohashes) and multisets (sets with multiplicity) in a way that they can be stored by the profiler and merged across time.
This JIRA should add:
* SET_INIT
* SET_ADD
* SET_REMOVE
* SET_MERGE
* MULTISET_INIT
* MULTISET_ADD
* MULTISET_REMOVE
* MULTISET_MERGE
* MULTISET_TO_SET
These follow the pattern of the other data structures (that are not stellar language primitives)
You can tinker with these in the stellar REPL as manual tests.
## Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our [Development Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235) for the complete guide to follow for contributions.
Please refer also to our [Build Verification Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview) for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
### For all changes:
- [x] Is there a JIRA ticket associated with this PR? If not one needs to be created at [Metron Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
- [x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
- [x] Has your PR been rebased against the latest commit within the target branch (typically master)?
### For code changes:
- [x] Have you included steps to reproduce the behavior or problem that is being changed or addressed?
- [x] Have you included steps or a guide to how the change may be verified and tested manually?
- [x] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
```
mvn -q clean integration-test install && build_utils/verify_licenses.sh
```
- [x] Have you written or updated unit tests and or integration tests to verify your changes?
- [x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?
### For documentation related changes:
- [x] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via `site-book/target/site/index.html`:
```
cd site-book
mvn site
```
#### Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that [travis-ci](https://travis-ci.org) is set up for your personal repository such that your branches are built there before submitting a pull request.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cestella/incubator-metron count_maps_for_stellar
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/metron/pull/728.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #728
----
commit 139d962af756a3f906d4bbcc7a7d8c8bab9d9299
Author: cstella <ce...@gmail.com>
Date: 2017-08-31T20:38:25Z
adding sets and multisets.
commit 83a08fc8a1b2c6d7426fdcea9166e49ffb2bb0f8
Author: cstella <ce...@gmail.com>
Date: 2017-09-01T01:16:56Z
tests added
commit 3683fc76151f0b126f8dc7d633e39c9e8eb4aa94
Author: cstella <ce...@gmail.com>
Date: 2017-09-01T14:46:55Z
Adding better docs and a MULTISET_TO_SET function.
----
> Add SET and MULTISET data structures to stellar
> -----------------------------------------------
>
> Key: METRON-1148
> URL: https://issues.apache.org/jira/browse/METRON-1148
> Project: Metron
> Issue Type: Improvement
> Reporter: Casey Stella
>
> With the addition of geohashes, to do analytics like tracking the statistical distribution of the distances of a user's login against the centroid of the user logins across some time, there is a need to be able to store sets (e.g. sets of geohashes) and multisets (sets with multiplicity) in a way that they can be stored by the profiler and merged across time.
> This JIRA should add:
> * SET_INIT
> * SET_ADD
> * SET_REMOVE
> * SET_MERGE
> * MULTISET_INIT
> * MULTISET_ADD
> * MULTISET_REMOVE
> * MULTISET_MERGE
> * MULTISET_TO_SET
> These follow the pattern of the other data structures (that are not stellar language primitives)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)