Re: WordDelimiterFilter+LenghtFilter results in termPosition==-1
Chris Hostetter wrote:
FYI: StopFilter already has an option to do this, but Solr doesn't make
thta option available when configuring it in the schema ... want to open
another bug for that? :)
Have a look at SOLR-521; I wrote a patch which activate it, and it works
("S.T.S." => "sts" in position 3, not 0)
Walter
[jira] Updated: (SOLR-521) Allow StopFilterFactory to use StopFilter setEnablePositionIncrementsDefault function
[ https://issues.apache.org/jira/browse/SOLR-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Walter Ferrara updated SOLR-521: Attachment: stopfilter.patch This patch add a boolean flag (enablePositionIncrements) for StopFilterTokenizer to use the setEnablePositionIncrementsDefault; after applying the patch you can modify your schema.xml as in: to use the new function. Default value is false. Notice that it acts on the static method StopFilter.setEnablePositionIncrementsDefault. > Allow StopFilterFactory to use StopFilter setEnablePositionIncrementsDefault > function > - > > Key: SOLR-521 > URL: https://issues.apache.org/jira/browse/SOLR-521 > Project: Solr > Issue Type: Improvement >Affects Versions: 1.3 >Reporter: Walter Ferrara >Priority: Trivial > Fix For: 1.3 > > Attachments: stopfilter.patch > > > Lucene StopFilter has a function, setEnablePositionIncrementsDefault, that > when set, "when a token is stopped (omitted), the position increment of the > following token is incremented". Solr however have no setting in schema.xml > to activate this -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SOLR-521) Allow StopFilterFactory to use StopFilter setEnablePositionIncrementsDefault function
Allow StopFilterFactory to use StopFilter setEnablePositionIncrementsDefault function - Key: SOLR-521 URL: https://issues.apache.org/jira/browse/SOLR-521 Project: Solr Issue Type: Improvement Affects Versions: 1.3 Reporter: Walter Ferrara Priority: Trivial Fix For: 1.3 Lucene StopFilter has a function, setEnablePositionIncrementsDefault, that when set, "when a token is stopped (omitted), the position increment of the following token is incremented". Solr however have no setting in schema.xml to activate this -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Solr nightly build failure
init-forrest-entities: [mkdir] Created dir: /tmp/apache-solr-nightly/build compile-common: [mkdir] Created dir: /tmp/apache-solr-nightly/build/common [javac] Compiling 31 source files to /tmp/apache-solr-nightly/build/common [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. compile: [mkdir] Created dir: /tmp/apache-solr-nightly/build/core [javac] Compiling 310 source files to /tmp/apache-solr-nightly/build/core [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. compile-solrj-core: [mkdir] Created dir: /tmp/apache-solr-nightly/build/client/solrj [javac] Compiling 22 source files to /tmp/apache-solr-nightly/build/client/solrj [javac] Note: /tmp/apache-solr-nightly/client/java/solrj/src/org/apache/solr/client/solrj/impl/CommonsHttpSolrServer.java uses or overrides a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. compile-solrj: [javac] Compiling 2 source files to /tmp/apache-solr-nightly/build/client/solrj compileTests: [mkdir] Created dir: /tmp/apache-solr-nightly/build/tests [javac] Compiling 88 source files to /tmp/apache-solr-nightly/build/tests [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. junit: [mkdir] Created dir: /tmp/apache-solr-nightly/build/test-results [junit] Running org.apache.solr.BasicFunctionalityTest [junit] Tests run: 25, Failures: 0, Errors: 0, Time elapsed: 28.082 sec [junit] Running org.apache.solr.ConvertedLegacyTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 17.238 sec [junit] Running org.apache.solr.DisMaxRequestHandlerTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 29.502 sec [junit] Running org.apache.solr.EchoParamsTest [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 8.659 sec [junit] Running org.apache.solr.OutputWriterTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 8.811 sec [junit] Running org.apache.solr.SampleTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.181 sec [junit] Running org.apache.solr.TestDistributedSearch [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 38.184 sec [junit] 2008-03-31 08:15:09.090::INFO: Shutdown hook executing [junit] 2008-03-31 08:15:09.091::INFO: Shutdown hook complete [junit] 2008-03-31 08:15:10.130::INFO: Shutdown hook complete [junit] 2008-03-31 08:15:11.133::INFO: Shutdown hook complete [junit] 2008-03-31 08:15:12.153::INFO: Shutdown hook complete [junit] 2008-03-31 08:15:13.153::INFO: Shutdown hook complete [junit] 2008-03-31 08:15:14.163::INFO: Shutdown hook complete [junit] 2008-03-31 08:15:15.172::INFO: Shutdown hook complete [junit] 2008-03-31 08:15:16.466::INFO: Shutdown hook complete [junit] 2008-03-31 08:15:17.613::INFO: Shutdown hook complete [junit] Running org.apache.solr.analysis.HTMLStripReaderTest [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 1.394 sec [junit] Running org.apache.solr.analysis.TestBufferedTokenStream [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.991 sec [junit] Running org.apache.solr.analysis.TestCapitalizationFilter [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.948 sec [junit] Running org.apache.solr.analysis.TestHyphenatedWordsFilter [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.079 sec [junit] Running org.apache.solr.analysis.TestKeepWordFilter [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.843 sec [junit] Running org.apache.solr.analysis.TestPatternReplaceFilter [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 2.819 sec [junit] Running org.apache.solr.analysis.TestPatternTokenizerFactory [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.572 sec [junit] Running org.apache.solr.analysis.TestPhoneticFilter [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 1.939 sec [junit] Running org.apache.solr.analysis.TestRemoveDuplicatesTokenFilter [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 1.701 sec [junit] Running org.apache.solr.analysis.TestSynonymFilter [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 3.534 sec [junit] Running org.apache.solr.analysis.TestTrimFilter [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.946 sec [junit] Running org.apache.solr.analysis.TestWordDelimiterFi
Hudson build is back to normal: Solr-trunk #393
See http://hudson.zones.apache.org/hudson/job/Solr-trunk/393/changes
[jira] Created: (SOLR-522) analysis.jsp doesn't show payloads created/modified by tokenizers and tokenfilters
analysis.jsp doesn't show payloads created/modified by tokenizers and tokenfilters -- Key: SOLR-522 URL: https://issues.apache.org/jira/browse/SOLR-522 Project: Solr Issue Type: Improvement Components: web gui Reporter: Tricia Williams Priority: Trivial Add payload content to the vebose output of the analysis.jsp page for debugging purposes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-522) analysis.jsp doesn't show payloads created/modified by tokenizers and tokenfilters
[ https://issues.apache.org/jira/browse/SOLR-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tricia Williams updated SOLR-522: - Attachment: SOLR-522-analysis.jsp.patch Added if block to analysis.jsp which converts the Payload's byte stream directly to a String for display. This might not suit the use case of all payloads so this may need to be revisited as those emerge. > analysis.jsp doesn't show payloads created/modified by tokenizers and > tokenfilters > -- > > Key: SOLR-522 > URL: https://issues.apache.org/jira/browse/SOLR-522 > Project: Solr > Issue Type: Improvement > Components: web gui >Reporter: Tricia Williams >Priority: Trivial > Attachments: SOLR-522-analysis.jsp.patch > > Original Estimate: 0.17h > Remaining Estimate: 0.17h > > Add payload content to the vebose output of the analysis.jsp page for > debugging purposes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SOLR-523) Solr Schema - version number requirements
Solr Schema - version number requirements
-
Key: SOLR-523
URL: https://issues.apache.org/jira/browse/SOLR-523
Project: Solr
Issue Type: Bug
Affects Versions: 1.2
Reporter: Andrew Nagy
Priority: Minor
When I change the version number of the solr schema from 1.0 or 1.1 to
something arbitrary like say 0.8.1 - solr reports a parsing error with the
schema - however, a version number "0.8" is accepted. It would be nice if solr
reporting an "invalid schema version" error instead or atleast put something in
the log that has a bit more detail.
You could add in a check in src/java/org/apache/solr/schema/IndexSchema.java
that might look like this:
Node node = (Node) xpath.evaluate("/schema/@version", document,
XPathConstants.NODE);
if (!("1.0".equals(node) || "1.1".equals(node))) {
log.warning("invalid schema version - use 1.0 or 1.1 only");
}
It's quite poor to hardcode the version numbers - but I thought I should
include something to give you a more concrete idea of what I am talking about.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-523) Solr Schema - version number requirements
[
https://issues.apache.org/jira/browse/SOLR-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583925#action_12583925
]
Hoss Man commented on SOLR-523:
---
schema version numbers really are specific and meaningful, just like Lucene
index format version number, so having a hardcoded set of legal version numbers
and warning if an unrecognized schema version is found makes sense to me.
> Solr Schema - version number requirements
> -
>
> Key: SOLR-523
> URL: https://issues.apache.org/jira/browse/SOLR-523
> Project: Solr
> Issue Type: Bug
>Affects Versions: 1.2
>Reporter: Andrew Nagy
>Priority: Minor
>
> When I change the version number of the solr schema from 1.0 or 1.1 to
> something arbitrary like say 0.8.1 - solr reports a parsing error with the
> schema - however, a version number "0.8" is accepted. It would be nice if
> solr reporting an "invalid schema version" error instead or atleast put
> something in the log that has a bit more detail.
> You could add in a check in src/java/org/apache/solr/schema/IndexSchema.java
> that might look like this:
> Node node = (Node) xpath.evaluate("/schema/@version", document,
> XPathConstants.NODE);
> if (!("1.0".equals(node) || "1.1".equals(node))) {
> log.warning("invalid schema version - use 1.0 or 1.1 only");
> }
> It's quite poor to hardcode the version numbers - but I thought I should
> include something to give you a more concrete idea of what I am talking about.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SOLR-524) snappuller has limitation w/r/t/ handling multiple web apps
snappuller has limitation w/r/t/ handling multiple web apps
---
Key: SOLR-524
URL: https://issues.apache.org/jira/browse/SOLR-524
Project: Solr
Issue Type: Improvement
Components: replication
Affects Versions: 1.2
Environment: Linux (CentOS release 5 (Final))
Java JDK 6
Reporter: Ezra Epstein
Priority: Minor
The snappuller has a limitation which makes it hard to use for replicating the
indices for multiple webapps. In particular, by changing:
# rsync over files that have changed
rsync -Wa${verbose}${compress} --delete ${sizeonly} \
${stats} rsync://${master_host}:${rsyncd_port}/solr/${name}/
${data_dir}/${name}-wip
to:
# rsync over files that have changed
rsync -Wa${verbose}${compress} --delete ${sizeonly} \
${stats} rsync://${master_host}:${rsyncd_port}/${rsync_module_path}/${name}/
${data_dir}/${name}-wip
and adding an rsync_module_path variable to scripts.conf, plus giving it a
default value of "solr" before the 'unset' commands at the top of the
snappuller script, I've worked around the issue. Still, it seems better to not
hard-code the module name ([solr]) and also to allow some flexibility in the
location of the data files under that module. This is req'd for multiple
webapps since they won't share a data folder.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-521) Allow StopFilterFactory to use StopFilter setEnablePositionIncrementsDefault function
[ https://issues.apache.org/jira/browse/SOLR-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583963#action_12583963 ] Hoss Man commented on SOLR-521: --- it would probably be better to use StopFilter.setEnablePositionIncrements instead of the version that changes the global variable. > Allow StopFilterFactory to use StopFilter setEnablePositionIncrementsDefault > function > - > > Key: SOLR-521 > URL: https://issues.apache.org/jira/browse/SOLR-521 > Project: Solr > Issue Type: Improvement >Affects Versions: 1.3 >Reporter: Walter Ferrara >Priority: Trivial > Fix For: 1.3 > > Attachments: stopfilter.patch > > > Lucene StopFilter has a function, setEnablePositionIncrementsDefault, that > when set, "when a token is stopped (omitted), the position increment of the > following token is incremented". Solr however have no setting in schema.xml > to activate this -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-502) Add search time out support
[ https://issues.apache.org/jira/browse/SOLR-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Timm updated SOLR-502: --- Attachment: solrTimeout.patch Added the ability to allows timeouts to occur on one or more shards in a distributed search (SOLR-303) and still be merged. The resulting set is reported as a partial result and is not cachable in an HTTP cache. This fixes the last known issue. > Add search time out support > --- > > Key: SOLR-502 > URL: https://issues.apache.org/jira/browse/SOLR-502 > Project: Solr > Issue Type: New Feature > Components: search >Reporter: Sean Timm >Priority: Minor > Attachments: SOLR-502-solrj.patch, solrTimeout.patch, > solrTimeout.patch, solrTimeout.patch, solrTimeout.patch, solrTimeout.patch > > > Uses LUCENE-997 to add time out support to Solr. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
