[jira] [Commented] (NUTCH-2353) Create seed file with metadata using the REST API

2017-01-21 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/NUTCH-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833139#comment-15833139
 ] 

ASF GitHub Bot commented on NUTCH-2353:
---

GitHub user jorgelbg opened a pull request:

https://github.com/apache/nutch/pull/175

Fix for NUTCH-2353 contributed by jorgelbg

This PR adds the possibility of adding metadata to the seed file created 
using the REST API as showed on 
https://issues.apache.org/jira/browse/NUTCH-2353, the supported syntax is:

```json
{
"name":"name-of-seedlist", 
"seedUrls":[
{
"url" : "http://example.com;,
"metadata" : {
"key1" : "value1",
"key2" : "value2",
"key3" : "value3"
}
}
]
}
```

Also the old syntax is supported:

```json
{
"name":"name-of-seedlist", 
"seedUrls":["http://www.example.com;, "http://www.example1.com;]
}
```

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jorgelbg/nutch NUTCH-2353

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nutch/pull/175.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 #175


commit 7deb576bc58bb74725cbb6c5d82d7b9244c6ad42
Author: Jorge Luis Betancourt 
Date:   2017-01-20T21:13:45Z

Fix for NUTCH-2353 contributed by jorgelbg




> Create seed file with metadata using the REST API
> -
>
> Key: NUTCH-2353
> URL: https://issues.apache.org/jira/browse/NUTCH-2353
> Project: Nutch
>  Issue Type: Improvement
>  Components: injector, REST_api
>Affects Versions: 1.12
>Reporter: Jorge Luis Betancourt Gonzalez
>Assignee: Jorge Luis Betancourt Gonzalez
>Priority: Minor
>  Labels: rest_api
> Fix For: 1.13
>
>
> At the moment its not possible to create a seed file and specify any metadata 
> when using the REST API. The file gets created but there is no option to add 
> any metadata to the seed URLs.
> If we use a payload like this:
> {code}
> {
> "name":"name-of-seedlist", 
> "seedUrls":[
> {
> "url" : "http://example.com;,
> "metadata" : {
> "key1" : "value1",
> "key2" : "value2",
> "key3" : "value3"
> }
> }
> ]
> }
> {code}
> It should be easy to specify the desired metadata. Also this should keep BC 
> with the previous array syntax if we only want to specify the list of URLs 
> without any metadata at all.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nutch pull request #175: Fix for NUTCH-2353 contributed by jorgelbg

2017-01-21 Thread jorgelbg 
GitHub user jorgelbg opened a pull request:

https://github.com/apache/nutch/pull/175

Fix for NUTCH-2353 contributed by jorgelbg

This PR adds the possibility of adding metadata to the seed file created 
using the REST API as showed on 
https://issues.apache.org/jira/browse/NUTCH-2353, the supported syntax is:

```json
{
"name":"name-of-seedlist", 
"seedUrls":[
{
"url" : "http://example.com;,
"metadata" : {
"key1" : "value1",
"key2" : "value2",
"key3" : "value3"
}
}
]
}
```

Also the old syntax is supported:

```json
{
"name":"name-of-seedlist", 
"seedUrls":["http://www.example.com;, "http://www.example1.com;]
}
```

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jorgelbg/nutch NUTCH-2353

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nutch/pull/175.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 #175


commit 7deb576bc58bb74725cbb6c5d82d7b9244c6ad42
Author: Jorge Luis Betancourt 
Date:   2017-01-20T21:13:45Z

Fix for NUTCH-2353 contributed by jorgelbg




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NUTCH-2346) Check Types at Object Equality

2017-01-21 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/NUTCH-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833122#comment-15833122
 ] 

Hudson commented on NUTCH-2346:
---

FAILURE: Integrated in Jenkins build Nutch-nutchgora #1579 (See 
[https://builds.apache.org/job/Nutch-nutchgora/1579/])
NUTCH-2346 Types are checked at object equality (kamaci: rev 
170f8c1375c8826c6397de0eb80e2fa29d2bfe5f)
* (edit) src/java/org/apache/nutch/crawl/GeneratorJob.java
* (edit) src/java/org/apache/nutch/metadata/Metadata.java


> Check Types at Object Equality
> --
>
> Key: NUTCH-2346
> URL: https://issues.apache.org/jira/browse/NUTCH-2346
> Project: Nutch
>  Issue Type: Bug
>  Components: generator, metadata
>Affects Versions: 2.3.1
>Reporter: Furkan KAMACI
>Assignee: Furkan KAMACI
>Priority: Minor
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Build failed in Jenkins: Nutch-nutchgora #1579

2017-01-21 Thread Apache Jenkins Server 
See 

Changes:

[kamaci] NUTCH-2346 Types are checked at object equality

--
[...truncated 1393 lines...]
deploy:

copy-generated-lib:

deploy:

copy-generated-lib:

init:

init-plugin:

deps-jar:

clean-lib:

resolve-default:
[ivy:resolve] :: loading settings :: file = 


compile:
 [echo] Compiling plugin: urlfilter-suffix
[javac] Compiling 1 source file to 


jar:
  [jar] Building jar: 


deps-test:

deploy:

copy-generated-lib:
 [copy] Copying 1 file to 


init:

init-plugin:

deps-jar:

clean-lib:

resolve-default:
[ivy:resolve] :: loading settings :: file = 


compile:
 [echo] Compiling plugin: urlfilter-validator

jar:

deps-test:

deploy:

copy-generated-lib:

init:

init-plugin:

deps-jar:

clean-lib:

resolve-default:
[ivy:resolve] :: loading settings :: file = 


compile:
 [echo] Compiling plugin: urlnormalizer-basic
[javac] Compiling 1 source file to 


jar:
  [jar] Building jar: 


deps-test:

deploy:

copy-generated-lib:
 [copy] Copying 1 file to 


init:

init-plugin:

deps-jar:

clean-lib:

resolve-default:
[ivy:resolve] :: loading settings :: file = 


compile:
 [echo] Compiling plugin: urlnormalizer-pass

jar:

deps-test:

deploy:

copy-generated-lib:

init:

init-plugin:

deps-jar:

clean-lib:

resolve-default:
[ivy:resolve] :: loading settings :: file = 


compile:
 [echo] Compiling plugin: urlnormalizer-regex
[javac] Compiling 1 source file to 


jar:
  [jar] Building jar: 


deps-test:

init:

init-plugin:

clean-lib:

resolve-default:
[ivy:resolve] :: loading settings :: file = 


compile:

jar:

deps-test:

deploy:

copy-generated-lib:

deploy:

copy-generated-lib:
 [copy] Copying 1 file to 


compile:

job:
  [jar] Building jar: 


resolve-test:
[ivy:resolve] 
[ivy:resolve] :: problems summary ::
[ivy:resolve]  ERRORS
[ivy:resolve]   unknown resolver main
[ivy:resolve] 
[ivy:resolve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
[ivy:retrieve]  conflict on 

 in [test]: 2.2.3 won
  [taskdef] Could not load definitions from resource org/sonar/ant/antlib.xml. 
It could not be found.

copy-libs:

compile-core-test:
[javac] Compiling 1 source file to 


test-core:
   [delete] Deleting directory 

[mkdir] Created dir: 

 [copy] Copying 94 files to 

[junit] Running org.apache.nutch.api.TestNutchAPI
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.636 sec
[junit] Running org.apache.nutch.crawl.TestAdaptiveFetchSchedule
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.668 sec
[junit] Running org.apache.nutch.crawl.TestGenerator
[junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 
7.893 sec
[junit] Running org.apache.nutch.crawl.TestInjector
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
7.685 sec
[junit] Running org.apache.nutch.crawl.TestSignatureFactory
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.276 sec
[junit] Running org.apache.nutch.crawl.TestURLPartitioner
[junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.226 sec
[junit] Running org.apache.nutch.crawl.TestUrlWithScore
[junit]

[jira] [Resolved] (NUTCH-2346) Check Types at Object Equality

2017-01-21 Thread Lewis John McGibbney (JIRA) 

 [ 
https://issues.apache.org/jira/browse/NUTCH-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lewis John McGibbney resolved NUTCH-2346.
-
Resolution: Fixed

Thanks [~kamaci]

> Check Types at Object Equality
> --
>
> Key: NUTCH-2346
> URL: https://issues.apache.org/jira/browse/NUTCH-2346
> Project: Nutch
>  Issue Type: Bug
>  Components: generator, metadata
>Affects Versions: 2.3.1
>Reporter: Furkan KAMACI
>Assignee: Furkan KAMACI
>Priority: Minor
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NUTCH-2346) Check Types at Object Equality

2017-01-21 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/NUTCH-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833096#comment-15833096
 ] 

ASF GitHub Bot commented on NUTCH-2346:
---

Github user asfgit closed the pull request at:

https://github.com/apache/nutch/pull/164


> Check Types at Object Equality
> --
>
> Key: NUTCH-2346
> URL: https://issues.apache.org/jira/browse/NUTCH-2346
> Project: Nutch
>  Issue Type: Bug
>  Components: generator, metadata
>Affects Versions: 2.3.1
>Reporter: Furkan KAMACI
>Assignee: Furkan KAMACI
>Priority: Minor
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nutch pull request #164: NUTCH-2346 Types are checked at object equality

2017-01-21 Thread asfgit 
Github user asfgit closed the pull request at:

https://github.com/apache/nutch/pull/164


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---