YAKESHRAJ M created METRON-1536:
---
Summary: Metron Build freezes at npm install
@metron-interface/metron-config
Key: METRON-1536
URL: https://issues.apache.org/jira/browse/METRON-1536
Project: Metron
YAKESHRAJ M created METRON-1537:
---
Summary: Vagrant Up becomes unsuccessfull after metron Build is
successfull
Key: METRON-1537
URL: https://issues.apache.org/jira/browse/METRON-1537
Project: Metron
GitHub user sardell opened a pull request:
https://github.com/apache/metron/pull/1001
METRON-1532: Getting started documentation improvements
## Contributor Comments
I added the documentation items mentioned here:
https://issues.apache.org/jira/browse/METRON-1532
## Pul
[
https://issues.apache.org/jira/browse/METRON-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447797#comment-16447797
]
ASF GitHub Bot commented on METRON-1532:
GitHub user sardell opened a pull reques
[
https://issues.apache.org/jira/browse/METRON-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447995#comment-16447995
]
Simon Elliston Ball commented on METRON-1537:
-
It looks like your machine, mo
Github user simonellistonball commented on the issue:
https://github.com/apache/metron/pull/1001
+1 thees are useful additions for anyone getting started.
---
[
https://issues.apache.org/jira/browse/METRON-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447996#comment-16447996
]
ASF GitHub Bot commented on METRON-1532:
Github user simonellistonball commented
Github user asfgit closed the pull request at:
https://github.com/apache/metron/pull/982
---
[
https://issues.apache.org/jira/browse/METRON-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448162#comment-16448162
]
ASF GitHub Bot commented on METRON-1511:
Github user asfgit closed the pull reque
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/995
For the integration test, adding the specific dynamic fields for the
underlying LatLon seems to take care of the problem for that type.
e.g. this makes the test you added pass:
```
[
https://issues.apache.org/jira/browse/METRON-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448176#comment-16448176
]
ASF GitHub Bot commented on METRON-1526:
Github user justinleet commented on the
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/995
Adding this dynamic field worked for me as well. I tested in a Solr
installation as well as the integration test. I believe this will solve our
issue with the older LatLon type. The only other f
[
https://issues.apache.org/jira/browse/METRON-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448305#comment-16448305
]
ASF GitHub Bot commented on METRON-1526:
Github user merrimanr commented on the i
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/995
The latest commit reverts the original fix in this PR, adds the extra
dynamic field to the existing schemas, and adds a section in the Solr README
documenting this for LatLon and PointType field ty
[
https://issues.apache.org/jira/browse/METRON-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448388#comment-16448388
]
ASF GitHub Bot commented on METRON-1526:
Github user merrimanr commented on the i
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/995
If we're going to the `docValues=false` + documentation route, we should
have the documentation be more generic than just the LatLon and Point (e.g.
custom types that may get used in more advance
[
https://issues.apache.org/jira/browse/METRON-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448644#comment-16448644
]
ASF GitHub Bot commented on METRON-1526:
Github user justinleet commented on the
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/990
Ok, @nickwallen I think I reacted to your comments. I'm going to spin this
up one more time since it's churned a bit since I originally submitted. Let me
know if I missed anything.
---
[
https://issues.apache.org/jira/browse/METRON-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448715#comment-16448715
]
ASF GitHub Bot commented on METRON-1520:
Github user cestella commented on the is
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/995
I'd be ok with going the `docValues=false` route, but I'm really curious as
to why other polytypes wouldn't have this issue. I'll hold for that
justification.
---
[
https://issues.apache.org/jira/browse/METRON-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448726#comment-16448726
]
ASF GitHub Bot commented on METRON-1526:
Github user cestella commented on the is
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/995
Just to clarify, both `docValues` and `stored` needs to be set to false.
If one or the other are true then it fails.
At this point I question whether a field being a polyfield is causing t
[
https://issues.apache.org/jira/browse/METRON-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448759#comment-16448759
]
ASF GitHub Bot commented on METRON-1526:
Github user merrimanr commented on the i
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/995
To give an idea of how I arrived at the conclusion that other fields are
not a problem, this is how I tested it. I will use currency as an example.
First I added this to our bro schema:
```
[
https://issues.apache.org/jira/browse/METRON-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448774#comment-16448774
]
ASF GitHub Bot commented on METRON-1526:
Github user merrimanr commented on the i
[
https://issues.apache.org/jira/browse/METRON-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448784#comment-16448784
]
ASF GitHub Bot commented on METRON-1526:
Github user merrimanr commented on the i
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/995
A note about the added integration test. I moved the test to the
SolrUpdateIntegrationTest because this issue is specific to Solr. Adding an
additional test exposed a problem in our Solr in memor
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/990
I reran this in full-dev from scratch and it checks out. Let me know if
there are any more comments @nickwallen and @ottobackwards
---
[
https://issues.apache.org/jira/browse/METRON-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448847#comment-16448847
]
ASF GitHub Bot commented on METRON-1520:
Github user cestella commented on the is
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/995
@merrimanr Let me replay my understanding to see if I'm on the right track.
The problem we have is that we're returning fields that we can't reindex as
a whole document when we run a glob
[
https://issues.apache.org/jira/browse/METRON-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448876#comment-16448876
]
ASF GitHub Bot commented on METRON-1526:
Github user justinleet commented on the
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/995
Thanks for the thorough reply @justinleet. Everything you have said makes
sense to me.
In my testing I also found copy fields to be an issue if they were set to
stored. Same problem as L
[
https://issues.apache.org/jira/browse/METRON-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448907#comment-16448907
]
ASF GitHub Bot commented on METRON-1526:
Github user merrimanr commented on the i
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/995
@justinleet - Thanks for that write up - that helps considerably.
Just to round out @merrimanr 's comment about polyfields:
>At this point I question whether a field being a polyfiel
[
https://issues.apache.org/jira/browse/METRON-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448987#comment-16448987
]
ASF GitHub Bot commented on METRON-1526:
Github user mmiklavc commented on the is
[
https://issues.apache.org/jira/browse/METRON-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449012#comment-16449012
]
ASF GitHub Bot commented on METRON-1520:
Github user nickwallen commented on the
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/990
+1 Thanks. Looks good.
---
[
https://issues.apache.org/jira/browse/METRON-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449235#comment-16449235
]
YAKESHRAJ M commented on METRON-1537:
-
[~simonellistonball] Thank you for your reply.
[
https://issues.apache.org/jira/browse/METRON-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449397#comment-16449397
]
Ali Nazemian commented on METRON-1103:
--
Looks like this issue is caused by source.ty
39 matches
Mail list logo
