[
https://issues.apache.org/jira/browse/SOLR-5594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878286#comment-13878286
]
Steve Rowe commented on SOLR-5594:
----------------------------------
bq. Once I figure out (or know) how to fix the EOL issue, I'll run ant
precommit to fix any further issues on that front.
In case you haven't figured it out yet, you just run {{svn propset
svn:eol-style native <file(s)>}}, where {{<file(s)>}} is the (list of) file(s)
that don't have the {{svn:eol-style}} property set on them. This info should
be on Lucene's and Solr's HowToContribute wiki pages, though I see it's not
there yet.
{quote}
Figured that out and ran it, only to run into the same issue twice over:
lucene-trunk2/lucene/common-build.xml:1851: java.lang.OutOfMemoryError: Java
heap space
{quote}
Line 1851 in {{lucene/common-build.xml}} runs the JTidy Ant task. According to
the comment on line 341:
{code:xml}
<!-- TODO: Fix this! For now only run this on 64bit, because jTIDY OOMs
with default heap size: -->
{code}
You can give arguments to the JVM that runs {{ant}} via the environment
variable {{ANT_OPTS}}. Here's mine (on Win7+Cygwin under bash):
{noformat}
export ANT_OPTS=-Xmx1100M -XX:MaxPermSize=256m -Dpython.exe=python2.6.exe
-Dpython32.exe=python3.2m.exe
{noformat}
I doubt the JTidy Ant task requires 1100MB, but the JFlex Ant task OOMs with
anything less than 1040MB on my box when it generates
{{UAX29URLEmailTokenizerImpl.java}} (via {{ant jflex}} under
{{lucene/analysis/common/}}, so that's why I have it set that high.
> Enable using extended field types with prefix queries for non-default encoded
> strings
> -------------------------------------------------------------------------------------
>
> Key: SOLR-5594
> URL: https://issues.apache.org/jira/browse/SOLR-5594
> Project: Solr
> Issue Type: Improvement
> Components: query parsers, Schema and Analysis
> Affects Versions: 4.6
> Reporter: Anshum Gupta
> Assignee: Anshum Gupta
> Priority: Minor
> Attachments: SOLR-5594-branch_4x.patch, SOLR-5594.patch,
> SOLR-5594.patch, SOLR-5594.patch, SOLR-5594.patch, SOLR-5594.patch,
> SOLR-5594.patch
>
>
> Enable users to be able to use prefix query with custom field types with
> non-default encoding/decoding for queries more easily. e.g. having a custom
> field work with base64 encoded query strings.
> Currently, the workaround for it is to have the override at getRewriteMethod
> level. Perhaps having the prefixQuery also use the calling FieldType's
> readableToIndexed method would work better.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
