[
https://issues.apache.org/jira/browse/JENA-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947680#comment-13947680
]
Brian McBride edited comment on JENA-654 at 3/26/14 8:48 AM:
-------------------------------------------------------------
My bad - there was a debug print statement left in. Another patch patch
attached. I thought the output was part of the testing framework - but it
wasn't.
The test output I see is:
[[
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.jena.query.text.TS_Text
08:45:53 WARN EntityDefinitionAssembler :: Failed to find a valid EntityMap
for : http://example.org/test/specNoMapProperty
08:45:53 WARN EntityDefinitionAssembler :: Failed to find a valid EntityMap
for : http://example.org/test/specNoDefaultField
08:45:53 WARN EntityDefinitionAssembler :: Failed to find a valid EntityMap
for : http://example.org/test/specNoEntityField
Tests run: 89, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.274 sec - in
org.apache.jena.query.text.TS_Text
Results :
Tests run: 89, Failures: 0, Errors: 0, Skipped: 0
]]
There are 3 warnings generated which are the same 3 as generated when I build
Jena text on the master branch.
I'm running Maven in Eclise Kepler Service Release 1
was (Author: bwm):
My bad - there was a debug print statement left in. I thought the output was
part of the testing framework - but it wasn't.
The test output I see is:
[[
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.jena.query.text.TS_Text
08:45:53 WARN EntityDefinitionAssembler :: Failed to find a valid EntityMap
for : http://example.org/test/specNoMapProperty
08:45:53 WARN EntityDefinitionAssembler :: Failed to find a valid EntityMap
for : http://example.org/test/specNoDefaultField
08:45:53 WARN EntityDefinitionAssembler :: Failed to find a valid EntityMap
for : http://example.org/test/specNoEntityField
Tests run: 89, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.274 sec - in
org.apache.jena.query.text.TS_Text
Results :
Tests run: 89, Failures: 0, Errors: 0, Skipped: 0
]]
There are 3 warnings generated which are the same 3 as generated when I build
Jena text on the master branch.
I'm running Maven in Eclise Kepler Service Release 1
> Enable jenatext to set the analyzer of a field.
> -----------------------------------------------
>
> Key: JENA-654
> URL: https://issues.apache.org/jira/browse/JENA-654
> Project: Apache Jena
> Issue Type: Improvement
> Components: Text
> Reporter: Brian McBride
> Priority: Minor
> Attachments:
> 0001-Added-configuration-of-text-analyzers-for-lucene-tex.patch,
> 0002-Added-configuration-of-Keyword-analyzer.patch,
> 0003-Fixed-test-errors-in-Maven-build.patch,
> 0004-Removed-left-over-debug-print-statement.patch,
> jena-654-text-query.mdtext.patch
>
>
> This issue was raised by Paul Tyson [1]
> The specific request is to be able to specify that a field should by analysed
> using Lucene's KeywordAnalyzer, though it is obvious that may generalized to
> specifying any analyzer.
> [1]
> http://mail-archives.apache.org/mod_mbox/jena-users/201403.mbox/%3C1394758305.5948.14.camel%40tristan%3E
--
This message was sent by Atlassian JIRA
(v6.2#6252)
