Re: [VOTE] 1.4 new RC up
On Mon, Nov 9, 2009 at 4:29 AM, Chris Hostetter wrote: > > : +1 for releasing these artifacts: > : > : 1cc3783316aa1f95ba5e250a4c1d0451 apache-solr-1.4.0.tgz > : 8da9395565736499f80542c8d05b3854 apache-solr-1.4.0.zip > > +1 from me for the same source artifacts. > > +1 -- Regards, Shalin Shekhar Mangar.
Re: [VOTE] 1.4 new RC up
+1 On Mon, Nov 9, 2009 at 8:34 AM, Erik Hatcher wrote: > +1 > > > On Nov 6, 2009, at 1:28 PM, Grant Ingersoll wrote: > >> OK, done. Same place as always. Looks like the Lucene release is finally >> going through, so let's get this finished up! >> >> On Nov 5, 2009, at 6:55 PM, Grant Ingersoll wrote: >> >>> Sure. I'll do it tonight or first thing tomorrow morning. >>> >>> >>> On Nov 5, 2009, at 6:04 PM, Yonik Seeley wrote: >>> On Thu, Nov 5, 2009 at 7:40 PM, Grant Ingersoll wrote: > > Hopefully, 4th time is the charm: > > http://people.apache.org/~gsingers/solr/1.4.0/ Can we respin???!!! https://issues.apache.org/jira/browse/SOLR-1543 -Yonik http://www.lucidimagination.com >>> >>> >> > > -- - Noble Paul | Principal Engineer| AOL | http://aol.com
[jira] Commented: (SOLR-1548) SolrPHP Library improvements
[
https://issues.apache.org/jira/browse/SOLR-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774876#action_12774876
]
Bill Bell commented on SOLR-1548:
-
addDocuments() - you can pass the cdataList and cdataSubList.
- cdataList is the list of fields like 'name'
- cdataSubList is the list of dynamic fields beginning with sm_field could
match sm_field_make, sm_field_model as an example
I didn't get to the control chars. But this should be added too -
function strip_ctl_chars($text) {
// See: http://w3.org/International/questions/qa-forms-utf-8.html
// Printable utf-8 does not include any of these chars below x7F
$text = preg_replace('@[\x00-\x08\x0B\x0C\x0E-\x1F]@', ' ', $text);
/*$output = '';
$slen = strlen($text);
echo "Check: $text\n";
for ($i = 0; $i < $slen; $i++) {
$v = ord($text[$i]);
if (($v >= 0 && $v <= 8) ||
($v == 11) ||
($v == 12) ||
($v == 14) ||
($v == 15) ||
($v >= 16 && $v <= 31)) {
echo "Found something!! " . $v . "\n";
$output .= ' ';
echo "set it:" . ord($output[$i]) . "\n";
} else {
$output .= $text[$i];
}
}
return $output; */
return $text;
}
How to use -
$cdataList = array("description", "name);
$cdataSubList = array("sm_field");
$solr->addDocuments($documents, false, true, true, $cdataList, $cdataSubList);
To get XML:
$str = $solr->_documentToXmlFragment( $document, $cdataList, $cdataSubList);
> SolrPHP Library improvements
>
>
> Key: SOLR-1548
> URL: https://issues.apache.org/jira/browse/SOLR-1548
> Project: Solr
> Issue Type: Improvement
> Components: clients - php
>Affects Versions: 1.4
> Environment: All
>Reporter: Bill Bell
> Attachments: SolrPhpClient.tar.gz
>
>
> 1. Adds the ability to specify CDATA fields
> 2. Since I like storing the XML as it is sent to SOLR - changes public the
> raw XML
> 3. Adds the ability to specify the fields to strip UTF-8 control characters
> to avoid problems
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-1548) SolrPHP Library improvements
[ https://issues.apache.org/jira/browse/SOLR-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bell updated SOLR-1548: Attachment: SolrPhpClient.tar.gz Fixes for several areas. > SolrPHP Library improvements > > > Key: SOLR-1548 > URL: https://issues.apache.org/jira/browse/SOLR-1548 > Project: Solr > Issue Type: Improvement > Components: clients - php >Affects Versions: 1.4 > Environment: All >Reporter: Bill Bell > Attachments: SolrPhpClient.tar.gz > > > 1. Adds the ability to specify CDATA fields > 2. Since I like storing the XML as it is sent to SOLR - changes public the > raw XML > 3. Adds the ability to specify the fields to strip UTF-8 control characters > to avoid problems -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SOLR-1548) SolrPHP Library improvements
SolrPHP Library improvements Key: SOLR-1548 URL: https://issues.apache.org/jira/browse/SOLR-1548 Project: Solr Issue Type: Improvement Components: clients - php Affects Versions: 1.4 Environment: All Reporter: Bill Bell 1. Adds the ability to specify CDATA fields 2. Since I like storing the XML as it is sent to SOLR - changes public the raw XML 3. Adds the ability to specify the fields to strip UTF-8 control characters to avoid problems -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-1547) TemplateTransformer should copy array/list more intelligently
[
https://issues.apache.org/jira/browse/SOLR-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-1547:
-
Attachment: SOLR-1547.patch
> TemplateTransformer should copy array/list more intelligently
> -
>
> Key: SOLR-1547
> URL: https://issues.apache.org/jira/browse/SOLR-1547
> Project: Solr
> Issue Type: Improvement
> Components: contrib - DataImportHandler
>Reporter: Noble Paul
>Priority: Minor
> Fix For: 1.5
>
> Attachments: SOLR-1547.patch
>
>
> if a field is copied TemplateTransformer does a toString()
> e.g
> {code:xml}
>
> {code}
> if slashdot.link is a List with a value http://somelink/ it would get copied
> as [http://somelink/]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SOLR-1547) TemplateTransformer should copy array/list more intelligently
TemplateTransformer should copy array/list more intelligently
-
Key: SOLR-1547
URL: https://issues.apache.org/jira/browse/SOLR-1547
Project: Solr
Issue Type: Improvement
Components: contrib - DataImportHandler
Reporter: Noble Paul
Priority: Minor
Fix For: 1.5
if a field is copied TemplateTransformer does a toString()
e.g
{code:xml}
{code}
if slashdot.link is a List with a value http://somelink/ it would get copied as
[http://somelink/]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [VOTE] 1.4 new RC up
+1 On Nov 6, 2009, at 1:28 PM, Grant Ingersoll wrote: OK, done. Same place as always. Looks like the Lucene release is finally going through, so let's get this finished up! On Nov 5, 2009, at 6:55 PM, Grant Ingersoll wrote: Sure. I'll do it tonight or first thing tomorrow morning. On Nov 5, 2009, at 6:04 PM, Yonik Seeley wrote: On Thu, Nov 5, 2009 at 7:40 PM, Grant Ingersoll wrote: Hopefully, 4th time is the charm: http://people.apache.org/~gsingers/solr/1.4.0/ Can we respin???!!! https://issues.apache.org/jira/browse/SOLR-1543 -Yonik http://www.lucidimagination.com
Re: [VOTE] 1.4 new RC up
+1 On Nov 6, 2009, at 2:25 PM, Yonik Seeley wrote: +1 for releasing these artifacts: 1cc3783316aa1f95ba5e250a4c1d0451 apache-solr-1.4.0.tgz 8da9395565736499f80542c8d05b3854 apache-solr-1.4.0.zip -Yonik http://www.lucidimagination.com On Fri, Nov 6, 2009 at 1:28 PM, Grant Ingersoll wrote: OK, done. Same place as always. Looks like the Lucene release is finally going through, so let's get this finished up! On Nov 5, 2009, at 6:55 PM, Grant Ingersoll wrote: Sure. I'll do it tonight or first thing tomorrow morning. On Nov 5, 2009, at 6:04 PM, Yonik Seeley wrote: On Thu, Nov 5, 2009 at 7:40 PM, Grant Ingersoll > wrote: Hopefully, 4th time is the charm: http://people.apache.org/~gsingers/solr/1.4.0/ Can we respin???!!! https://issues.apache.org/jira/browse/SOLR-1543 -Yonik http://www.lucidimagination.com
[jira] Commented: (SOLR-1546) When querying solrj the SolrServerException's cause is null
[
https://issues.apache.org/jira/browse/SOLR-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774838#action_12774838
]
Jake Brownell commented on SOLR-1546:
-
Sure, I was using the third 1.4 release candidate at the time. Hopefully this
stack trace is helpful. I guess the summary is slightly misleading, the cause
on the original caught exception is populated, it's just not possible to find
the ParseException if you climb the exception chain.
{noformat}
Caused by: org.apache.solr.client.solrj.SolrServerException: Error executing
query
at
org.apache.solr.client.solrj.request.QueryRequest.process(QueryRequest.java:95)
at org.apache.solr.client.solrj.SolrServer.query(SolrServer.java:118)
at
org.bookshare.search.solr.SolrSearchServerWrapper.query(SolrSearchServerWrapper.java:98)
... 32 more Caused by: org.apache.solr.common.SolrException:
org.apache.lucene.queryParser.ParseException: Cannot parse 'OR dad':
Encountered " "OR ""
at line 1, column 0. org.apache.lucene.queryParser.ParseException: Cannot parse
'OR dad': Encountered " "OR ""
at line 1, column 0. request:
http://localhost:8080/solr/select?q.alt=*:*&qt=dismax&qf=title^2.0&qf=title_phonetic^0.8&qf=author^2.0&qf=author_phonetic^0.8&qf=isbn^3.0&qf=content^1.0&pf=title^2.0&pf=title_phonetic^0.8&pf=author^2.0&pf=author_phonetic^0.8&pf=content^1.0&tie=0.1&q=OR
dad&fl=author,title,id,brief_synopsis,copyright_date,publish_date,format,grade,publisher,state,adult,demo,freely_available,nimac&rows=25&start=0&fq=(quality:2
OR quality:3 OR quality:0) AND
state:5&hl=true&hl.snippets=3&hl.fl=content_highlight&facet=true&facet.field=author_exact&f.author_exact.facet.method=fc&f.author_exact.facet.limit=20&f.author_exact.facet.offset=0&f.author_exact.facet.mincount=1&f.author_exact.facet.sort=true&debugQuery=false&wt=javabin&version=1
at
org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:424)
at
org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:243)
at
org.apache.solr.client.solrj.request.QueryRequest.process(QueryRequest.java:89)
... 34 more
org.apache.solr.client.solrj.solrserverexcept...@3a498c[
org.apache.solr.client.solrj.SolrServerException: Error executing query
at
org.apache.solr.client.solrj.request.QueryRequest.process(QueryRequest.java:95)
at org.apache.solr.client.solrj.SolrServer.query(SolrServer.java:118)
at
org.bookshare.search.solr.SolrSearchServerWrapper.query(SolrSearchServerWrapper.java:98)
at org.bookshare.search.solr.SolrSearchEngine.search(SolrSearchEngine.java:256)
at
org.bookshare.web.servlet.mvc.BetaAwesomeSearchController.search(BetaAwesomeSearchController.java:425)
at
org.bookshare.web.servlet.mvc.BetaAwesomeSearchController.onSubmit(BetaAwesomeSearchController.java:168)
at
org.springframework.web.servlet.mvc.SimpleFormController.processFormSubmission(SimpleFormController.java:267)
at
org.springframework.web.servlet.mvc.AbstractFormController.handleRequestInternal(AbstractFormController.java:265)
at
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
at
org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
at
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:875)
at
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809)
at
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571)
at
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:501)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:114)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:91)
at
com.caucho.server.dispatch.ServletFilterChain.doFilter(ServletFilterChain.java:103)
at
org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:359)
at
org.springframework.web.filter.AbstractRequestLoggingFilter.doFilterInternal(AbstractRequestLoggingFilter.java:156)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at
org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:371)
at
org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at
org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:371)
at
org.springframework.security.util.FilterChainProxy.doFilter(FilterChainProxy.java:174)
at
org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:236)
at
org.springframework.web.filter.DelegatingFilterProxy.do
[jira] Commented: (SOLR-1546) When querying solrj the SolrServerException's cause is null
[
https://issues.apache.org/jira/browse/SOLR-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774836#action_12774836
]
Hoss Man commented on SOLR-1546:
It would be helpful if you could post the stacktraces for the exception(s) you
are seeing where there is no nested clause but you feel like there should be --
that way we'd have methods and line numbers of where the Exception originalted
in order to determine why the cause isn't being set properly.
the current bug description feels like a needle in a hay stack.
> When querying solrj the SolrServerException's cause is null
> ---
>
> Key: SOLR-1546
> URL: https://issues.apache.org/jira/browse/SOLR-1546
> Project: Solr
> Issue Type: Improvement
> Components: clients - java
>Affects Versions: 1.4
> Environment: solrj
>Reporter: Jake Brownell
>Priority: Minor
>
> Our application processes queries like so:
> {code}
> try {
> final SolrServer server = getServer();
> final QueryResponse resp = server.query(query);
> return resp;
> } catch (final SolrServerException e) {
> /// bad things probably happened, invoke error processing and
> possibly switch to the backup
> }
> {code}
> Given SOLR-874 with dismax queries sometimes causing ParseException from
> Lucene, I'd like to be able to interrogate the cause chain of the
> SolrServerException. For example if I found ParseException in the chain, I
> could provide a specific error message and know that it's not necessary to
> switch to the backup server.
> As it is now, getCause is giving null. The undesirable fix right now is
> looking inside the toString/description for the "ParseException" phrase.
> Thanks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [VOTE] 1.4 new RC up
On Nov 8, 2009, at 5:59 PM, Chris Hostetter wrote: : +1 for releasing these artifacts: : : 1cc3783316aa1f95ba5e250a4c1d0451 apache-solr-1.4.0.tgz : 8da9395565736499f80542c8d05b3854 apache-solr-1.4.0.zip +1 from me for the same source artifacts. +1 for me.
Re: SEVERE: SolrIndexWriter was not closed prior to finalize
: that's what I thought because I didn't experience any problems. But doesn't : that indicate that there is a missing cleanup? yes, it does. : And if it is not worth checking / changing then maybe the log level should be : decreased to adjust in comparison to other SEVERE warnings? it really is an indication of a severe problem -- but unfortunately it's an indication of a problem detected during GC, which was was dealt with. the reason it's classified as SEVERE is because it's possible whatever caused this problem may be resulting in a resource leak which is *not* being detected. It would be really helpful if people seeing these messages frequently in their logs could elaborate a little bit more on... 1) exactly which version/build of Solr they are using 2) whether they have any custom plugins loaded (either that they developed on their own, or from a third party, or even from solr/contrib) 3) what types of funtionality of Solr they use when dealing with indexing (ie: DIH, CSV loading, Solr Cell, SignatureUpdateProcessor, etc...) Because this problem is only detected during GC, the log messages arround when it happens are probably not directly helpful, but a better picture of the *pattern* of behaviors that trigger this would be very helpful. The one thing i do notice in particular about the log messages that were posted in this thread is that the rollback feature was used ... is this a common pattern? ... do all of the people noticing these "POSSIBLE RESOURCE LEAK" messages use rollback? is there any correlation between how much you use rollback and how often you get one of these messages? (even if they don't happen at/near the same times) : It's just that monitoring systems will of course raise an alarm on SEVERE : messages. And even if SOLR runs perfect these messages would give the : impression that something's going wrong. (solr isn't running perfectly, and something is goig wrong, but luckily it's going wrong in a way that solr can recover from ... it could just as easily go wrong in a way that solr can't recover from) -Hoss
Re: [VOTE] 1.4 new RC up
: +1 for releasing these artifacts: : : 1cc3783316aa1f95ba5e250a4c1d0451 apache-solr-1.4.0.tgz : 8da9395565736499f80542c8d05b3854 apache-solr-1.4.0.zip +1 from me for the same source artifacts. -Hoss
