1st. You are not only one looking at the list on Dec 24th Casey, so don’t
feel bad.
2nd. Maybe we can separate this into 2 areas of concern.
1. Stellar can load objects into ‘caches’ from some repository and refer to
them.
2. The repositories
3. Some number of strategies to populate and
Oh, one more thing, while the example here is around typosquatting, this is
of use outside of that. Pretty much any large existence-style query can be
enabled via this construction (create a summary bloom filter). There are
other use-cases involving other data structures too.
On Sun, Dec 24,
I'll start this discussion off with my idea around a 2nd step that is more
adaptable. I propose the following set of stellar functions backed by
Spark in the metron-management project:
- CSV_PARSE(location, separator?, columns?) : Constructs a Spark
Dataframe for reading the flatfile
-
Hi all,
I wanted to get some feedback on a sensible plan for something. It
occurred to me the other day when considering the use-case of detecting
typosquatted domains, that one approach was to generate the set of
typosquatted domains for some set of reference domains and compare domains
as they
I'm gonna let this percolate until Wednesday or so, assuming conversation
doesn't reach a natural tipping point. I'm inclined to agree with Nick,
but I also don't want to resolve anything in a way that even potentially
causes master problems until at least after Christmas has a chance to
settle
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/879
After more consideration and more egg nog, I decided that I'd create a
DISCUSS thread about this entire use-case. We can move the discussion there.
---
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/879
Also, a wizard-like UI could simplify this dramatically. That was one of
the thoughts around extending and reusing the existing infrastructure in the
first pass of this rather than creating a new
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/879
@ottobackwards Yes, that's spot on. It's to enable creation of
summarization objects in a method similar (and reusing the configs and
infrastructure of) the flat file loader. The idea is that
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/879
@nickwallen I definitely hear you, the JSON configs are more complex than
I'd like. I'd like another more composable solution available using lambda
functions available in the REPL.
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/879
I think the need is to 'pre-create' complex objects, and re-use them across
multiple stellar rule executions, with the bloom-filter being the example.
Is that close?
> 3) I have been manually making submissions dating back to 2017-02-13, but
Oh, great.
So your general impression based on those submissions is that this would
be useful for us?
I didn't realize that you had already been reviewing the output of the tool
over a period of time.
Thanks, Jon
On
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/879
IMHO, this seems really complex. That JSON configuration looks really
scary to me and sadly I don't think I could bring myself to use this.
Fundamentally the need you are addressing is
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/526
What is the status of this pr? Can it be closed? I has no updates since
August and it is conflicted.
---
13 matches
Mail list logo
