Hm, now that is interesting. I'm not clear how they manage their URLs, but
it seems like they may have missed a hardcoded value used by their update
functionality.
On Feb 5, 2018 3:01 PM, "Nick Allen" wrote:
> I was experiencing this issue with both Ansible 1.8.1 and 2.0.2.
I was experiencing this issue with both Ansible 1.8.1 and 2.0.2.
I just found that now it seems to only spit out that warning when checking
for updates; not when downloading new images. If I remove the older image
to force it to re-download, it does seem to work. But after re-downloading
the
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/922
I would say collection for each parser and an error collection. It's
similar to ES templates where we define fields, types, etc.
---
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/922
So, the idea is that we have a 'core' for each parser? and for errors?
---
GitHub user mmiklavc opened a pull request:
https://github.com/apache/metron/pull/926
METRON-1446: Fix openjdk issue with Ubuntu
## Contributor Comments
https://issues.apache.org/jira/browse/METRON-1446
Spin up full dev for Ubuntu. It should run successfully all the way
I had this problem on a machine running Vagrant 1.8.1. I thought it was
only Ubuntu at first, so I removed some additional boxes and found it to be
a problem for all of them. I didn't see any relevant articles other than
some old stuff talking about a bundled curl command being a problem, but
that
I'd created a Jira awhile ago, but it deserves a callout to the community.
Especially if someone wants to grab it, it's probably something pretty easy
(and valuable!) to do.
There's a set of required links on Apache web pages, which can be seen
at Website
Navigation Links Policy
Github user asfgit closed the pull request at:
https://github.com/apache/metron/pull/923
---
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/922
@merrimanr Things should be fixed at this point. I'm going to spin it up
and validate things this morning.
---
I think that is fine, we can use that and work out the UX to manage new or
replace. Maybe we can do Profile Compare down the line?
On February 5, 2018 at 09:28:16, Nick Allen (n...@nickallen.org) wrote:
> If we replay a set of data with a new version of a profile I think it
will always have to
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/922
@merrimanr Ah! Yes, we really should set a `guid` field for errors.
---
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/922
The errors I found happened when I tried to create collections with each
schema. The error related to the `guid` field happens because it is defined as
the unique key but not included in the list
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/915
@mraliagha Nah, they're not a troublemaker. I'm removing the PR since
there's interest in them staying turned on by default.
---
Github user cestella closed the pull request at:
https://github.com/apache/metron/pull/915
---
> If we replay a set of data with a new version of a profile I think it
will always have to be a new profile and not ‘replace’ the old one.
Series1, Seriers2 etc?
As part of this effort (unless there is a compelling reason) I wouldn't
change that behavior. The profile data is stored based on
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/922
@merrimanr I'm confused about the guid field. I had to take that out given
the sample data that I generated from full-dev (they didn't have a `guid`
field). How did you create the errors?
---
Github user asfgit closed the pull request at:
https://github.com/apache/metron/pull/925
---
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/924#discussion_r165982935
--- Diff:
metron-platform/metron-common/src/test/java/org/apache/metron/common/error/MetronErrorTest.java
---
@@ -53,7 +52,14 @@ public void
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/925
https://issues.apache.org/jira/browse/METRON-1444
---
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/925
+1 by inspection
---
When launching either of the development environments, you are probably
seeing a warning message like this.
Bringing machine 'node1' up with 'virtualbox' provider...
> ...
> ==> node1: There was a problem while downloading the metadata for your box
> ==> node1: to check for updates. This is not
Thanks, Simon.
On 5 Feb. 2018 22:00, "Simon Elliston Ball"
wrote:
> I expect the performance would be dire. If you really wanted to do
> something like this, a custom writer might make sense. KAFKA_PUT is really
> meant for debugging use cases only. It’s a very
I expect the performance would be dire. If you really wanted to do something
like this, a custom writer might make sense. KAFKA_PUT is really meant for
debugging use cases only. It’s a very non-stellar construct (non-expression, no
return, side-effect dependent…) Also, it creates a producer for
23 matches
Mail list logo