Re: start.jar -Djetty.port= not working

[Mike Davies]

Hi Brian,

Found the SVN location, will download from there and give it a try.

Thanks for the help.



On 07/11/2007, Mike Davies <[EMAIL PROTECTED]> wrote:
>
> I'm using 1.2, downloaded from
>
> http://apache.rediris.es/lucene/solr/
>
> Where can i get the trunk version?
>
>
>
>
> On 07/11/2007, Brian Whitman <[EMAIL PROTECTED]> wrote:
> >
> >
> > On Nov 7, 2007, at 10:00 AM, Mike Davies wrote:
> > > java -Djetty.port=8521 -jar start.jar
> > >
> > > However when I run this it seems to ignore the command and still
> > > start on
> > > the default port of 8983.  Any suggestions?
> > >
> >
> > Are you using trunk solr or 1.2? I believe 1.2 still shipped with an
> > older version of jetty that doesn't follow the new-style CL
> > arguments. I just tried it on trunk and it worked fine for me.
> >
> >
> >
> >
> >
> >
> >
> > --
> > http://variogr.am/
> > [EMAIL PROTECTED]
> >
> >
> >
> >
>

start.jar -Djetty.port= not working

[Mike Davies]

Hi,

I'm trying to change the port number that the start.jar application runs
on.  I have found examples on the web that use the -Djetty.port=command,
i.e.

java -Djetty.port=8521 -jar start.jar

However when I run this it seems to ignore the command and still start on
the default port of 8983.  Any suggestions?

Also, I'd really like to get hold of the source code to the start.jar but I
cant seem to find it anywhere.  Again, any suggestions?

Thanks

Mike

Re: start.jar -Djetty.port= not working

[Mike Davies]

I'm using 1.2, downloaded from

http://apache.rediris.es/lucene/solr/

Where can i get the trunk version?




On 07/11/2007, Brian Whitman <[EMAIL PROTECTED]> wrote:
>
>
> On Nov 7, 2007, at 10:00 AM, Mike Davies wrote:
> > java -Djetty.port=8521 -jar start.jar
> >
> > However when I run this it seems to ignore the command and still
> > start on
> > the default port of 8983.  Any suggestions?
> >
>
> Are you using trunk solr or 1.2? I believe 1.2 still shipped with an
> older version of jetty that doesn't follow the new-style CL
> arguments. I just tried it on trunk and it worked fine for me.
>
>
>
>
>
>
>
> --
> http://variogr.am/
> [EMAIL PROTECTED]
>
>
>
>

Carrage Returns in XML Results

[Mike Davies]

Hi,

I'm having a small problem with Solr, have had a good look for solutions on
the web but nothing so far.  Apologies if this has been asked before.

I am indexing a text field to contain a text article, this article has some
line feeds and CR's in it.  I can index the field OK and if I look at the
Lucene index using Luke I can see that the CR + LF are being stored
correctly in the index, however, when I get the document back from Solr in
XML, the CR + LF's are missing.

Is there a way I can tell Solr to return the text as it appears in the
index, including the CR + LF's?

Thanks in advance

Mike

Re: Carrage Returns in XML Results

[Mike Davies]

Have resolved the problem.

Turns out it was not a problem with Solr but with SolrSharp, before loading
the XML stream into the parser it was removing all \n's from the server
response.

I've disabled this line and everything seems to be working now.

For anyone's future reference, change the following line in G
etXmlDocumentFromPost()

From:
xdoc.LoadXml(sr.Replace("\n", ""));

To:
xdoc.LoadXml(sr);

Cheers

Mike

On Feb 6, 2008 12:54 PM, Mike Davies <[EMAIL PROTECTED]> wrote:

> Hi,
>
> I'm having a small problem with Solr, have had a good look for solutions
> on the web but nothing so far.  Apologies if this has been asked before.
>
> I am indexing a text field to contain a text article, this article has
> some line feeds and CR's in it.  I can index the field OK and if I look at
> the Lucene index using Luke I can see that the CR + LF are being stored
> correctly in the index, however, when I get the document back from Solr in
> XML, the CR + LF's are missing.
>
> Is there a way I can tell Solr to return the text as it appears in the
> index, including the CR + LF's?
>
> Thanks in advance
>
> Mike
>