Re: DIH delta, deltaQuery

[Sven Almgren]

Are you running optimization after this query?

If you check the command=status page I'd guess that the document count
has stopped after a few seconds?

/Sven

On Wed, Nov 24, 2010 at 13:06, stockii  wrote:
>
> Hello.
>
> i wonder why this deltaQuery takes over a minute:
>
> deltaQuery="SELECT id FROM sessions
>                WHERE created BETWEEN DATE_ADD( NOW(), INTERVAL - 1 HOUR ) AND 
> NOW()
>                OR modified BETWEEN '${dataimporter.sessions 
> .last_index_time}' AND
> DATE_ADD( NOW(), INTERVAL - 1 HOUR  ) "
>
> the database have only 700 Entries and the compare with modified takes so
> long !!? when i remove the modified compare its fast.
>
> when i put this query in my mysql database the query need 0.0014 seconds
> ... wha is it so slow?
> --
> View this message in context: 
> http://lucene.472066.n3.nabble.com/DIH-delta-deltaQuery-tp1960246p1960246.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>

MoreLikeThis and two field in mlt.fl

[Damien Fontaine]

Hello,

I have a problem with MoreLikeThis on Solr 1.4.1. I can't put two field 
on mlt.fl.

Example : text and title, only text is in interestingTerms

/Damien

Re: How to use polish stemmer - Stempel - in schema.xml?

[Jakub Godawa]

After all I choose hunspell-solr as a Polish language interpreter. It
"understands" Polish and is much easier to install. But look out! I does
not work with current nightly build - works good with solr 1.4.1!

It just works well, and hey! I got Ukrainian out of the box too. I am
thinking of replacing all required lanugages' SnowballPorterFilters with
*.aff and *.dic support.

Thanks for the help everyone!

On Wed, 2010-11-24 at 19:00 +0100, Jakub Godawa wrote:
> Yes, from the current nightly release setting up Stempel is quite easy.
> 
> All I did was:
> 
> svn co https://svn.apache.org/repos/asf/lucene/dev/trunk ./lucene-solr
> 
> cd lucene-solr/solr
> ant example
> 
> cp 
> ./contrib/analysis-extras/lucene-libs/lucene-analyzers-stempel-4.0-SNAPSHOT.jar
>  ./lib
> cp 
> ./contrib/analysis-extras/build/apache-solr-analysis-extras-4.0-SNAPSHOT.jar 
> ./lib
> 
> in solrschema.xml
> 
> 
> 
> 
> in schema.xml
> 
> 
> 
>   
> 
> 
> 
> 
>  language="Polish" />
>   
> 
> 
> The end.
> 
> Anyway. I don't know if that is Polish stemmer or bad configurated
> fieldType, but the results are just wrong.
> 
> example:
> 
> index for type "text_pl": bilety
> query for type "text_pl": bilet
>  
> Index Analyzer
> 
> org.apache.solr.analysis.StempelPolishStemFilterFactory
> {language=Polish, luceneMatchVersion=LUCENE_24}
> term position
> 1
> term text
> bilić
> term type
> word
> source start,end
> 0,6
> payload
> 
> Query Analyzer
> 
> org.apache.solr.analysis.StempelPolishStemFilterFactory
> {language=Polish, luceneMatchVersion=LUCENE_24}
> term position
> 1
> term text
> binąć
> term type
> word
> source start,end
> 0,5
> payload
> 
> 
> But I imagine the result as: bilet and bilet which are the base.
> 
> Any clues how to make it work like Polish? Maybe someone has good
> experience with hunspell-solr and Polish dictonaries?
> 
> Thanks for letting me know!
> 
> Cheers,
> Jakub Godawa.
> 
> 
> 
> 
> On Mon, 2010-11-15 at 08:35 -0500, Robert Muir wrote:
> > https://issues.apache.org/jira/browse/SOLR-2237
> > 
> > On Mon, Nov 15, 2010 at 5:04 AM, Jakub Godawa 
> > wrote:
> > > I tried to reach the autors twice, but with no luck. I've seen some
> > > posts where people finally were able to lunch it (without much
> > pain).
> > > I don't know. If any pro would be so nice to try to run the stempel
> > on
> > > his/her machine and paste me some verbose step by step solution I
> > > would really appreciate.
> > >
> > > Cheers,
> > > Jakub Godawa.
> > >
> > > 2010/11/13 Lance Norskog :
> > >> I don't know of the Stempel jar includes the Java source. At this
> > point I
> > >> think you should ask the author to Stempel to make a Solr front-end
> > for it.
> > >> It's very simple for him.
> > >>
> > >> Jakub Godawa wrote:
> > >>>
> > >>> Am I not doing it in the point no 4? I am compiling all the folder
> > >>> that was extracted before, but now with that new class file.
> > >>>
> > >>> 2010/11/12 Lance Norskog:
> > >>>
> > 
> >  I think you have to compile all of the stempel source including
> > your
> >  filter factory into one jar at the same time. Everybody does
> > this; I
> >  don't know how different Java versions make class file binaries.
> > 
> >  On Thu, Nov 11, 2010 at 3:06 AM, Jakub
> > Godawa
> >   wrote:
> > 
> > >
> > > Hi! Sorry for such a break, but I was moving house... anyway:
> > >
> > > 1. I took the
> > >
> > ~/apache-solr/src/java/org/apache/solr/analysis/StandardFilterFactory.java
> > > file and modified it (named as StempelFilterFactory.java) in Vim
> > that
> > > way:
> > >
> > > package org.getopt.solr.analysis;
> > >
> > > import org.apache.lucene.analysis.TokenStream;
> > > import org.apache.lucene.analysis.standard.StandardFilter;
> > >
> > > public class StempelTokenFilterFactory extends
> > BaseTokenFilterFactory {
> > >  public StempelFilter create(TokenStream input) {
> > >return new StempelFilter(input);
> > >  }
> > > }
> > >
> > > 2. Then I put the file to the extracted stempel-1.0.jar in
> > > ./org/getopt/solr/analysis/
> > > 3. Then I created a class from it: jar -cf
> > > StempelTokenFilterFactory.class StempelFilterFactory.java
> > > 4. Then I created new stempel-1.0.jar archive: jar -cf
> > stempel-1.0.jar
> > > -C ./stempel-1.0/ .
> > > 5. Then in schema.xml I've put:
> > >
> > >
> > >  
> > >
> > >
> > > > > class="org.getopt.solr.analysis.StempelTokenFilterFactory" />
> > >  
> > >
> > >
> > > 6. I started the solr server and I recieved the following error:
> > >
> > > 2010-11-11 11:50:56 org.apache.solr.common.SolrException log
> > > SEVERE: java.lang.ClassFormatError: Incompatible magic value
> > > 1347093252 in class file
> > > org/getopt/solr/analysis/StempelTokenFilterFactory
> > >at java.lang.ClassLoader.defin

SOLR 1.4.1 : Indexing DateField time zone problem

[Shanmugavel SRD]

I am using SOLR 1.4.1. My SOLR runs in a server which is in EST zone.
I am trying to index a date field which is in MySQL as
'2007-08-08T05:36:50Z' but while indexing it becomes '2007-08-08T09:36:50Z'
where 4 hours got increased. But I want the date as is while indexing,
means, after indexing I want the value as '2007-08-08T05:36:50Z' in
'modified_d' field.

Can anyone help me on this?



I searched in this forum and there are discussions on this same problem but
on SOLR 1.3, that's why I am posting this query again.
-- 
View this message in context: 
http://lucene.472066.n3.nabble.com/SOLR-1-4-1-Indexing-DateField-time-zone-problem-tp1966118p1966118.html
Sent from the Solr - User mailing list archive at Nabble.com.

DIH : Delta import don't process the updated documents

[yaumix]

Hi,

I want to use the delta import, then i have configured the DIH like this :






























   




When i use the delta import, i get this response :

21
20
0
2010-11-25 13:59:44
2010-11-25 13:59:44
2010-11-25 13:59:44
2010-11-25 13:59:44
20
0
0:0:0.594

and in the logs :
INFO: Starting Delta Import
25 nov. 2010 13:59:44 org.apache.solr.core.SolrCore execute
INFO: [] webapp=/bricmlmc-search path=/select
params={clean=false&commit=true&command=delta-import&qt=/dataimport}
status=0 QTime=172 
25 nov. 2010 13:59:44 org.apache.solr.handler.dataimport.SolrWriter
readIndexerProperties
INFO: Read dataimport.properties
25 nov. 2010 13:59:44 org.apache.solr.handler.dataimport.DocBuilder doDelta
INFO: Starting delta collection.
25 nov. 2010 13:59:44 org.apache.solr.handler.dataimport.DocBuilder
collectDelta
INFO: Running ModifiedRowKey() for Entity: content
25 nov. 2010 13:59:44 org.apache.solr.handler.dataimport.DocBuilder
collectDelta
INFO: Completed ModifiedRowKey for Entity: content rows obtained : 0
25 nov. 2010 13:59:44 org.apache.solr.handler.dataimport.DocBuilder
collectDelta
INFO: Completed DeletedRowKey for Entity: content rows obtained : 0
25 nov. 2010 13:59:44 org.apache.solr.handler.dataimport.DocBuilder
collectDelta
INFO: Completed parentDeltaQuery for Entity: content
25 nov. 2010 13:59:44 org.apache.solr.handler.dataimport.DocBuilder
collectDelta
INFO: Running ModifiedRowKey() for Entity: flux
25 nov. 2010 13:59:44 org.apache.solr.handler.dataimport.DocBuilder
collectDelta
INFO: Completed ModifiedRowKey for Entity: flux rows obtained : 0
25 nov. 2010 13:59:44 org.apache.solr.handler.dataimport.DocBuilder
collectDelta
INFO: Completed DeletedRowKey for Entity: flux rows obtained : 0
25 nov. 2010 13:59:44 org.apache.solr.handler.dataimport.DocBuilder
collectDelta
INFO: Completed parentDeltaQuery for Entity: flux
25 nov. 2010 13:59:44 org.apache.solr.handler.dataimport.DocBuilder
collectDelta
INFO: Running ModifiedRowKey() for Entity: contrat
25 nov. 2010 13:59:44 org.apache.solr.handler.dataimport.JdbcDataSource$1
call
INFO: Creating a connection for entity contrat with URL:
jdbc:oracle:thin:@localhost:1521:XE
25 nov. 2010 13:59:44 org.apache.solr.handler.dataimport.JdbcDataSource$1
call
INFO: Time taken for getConnection(): 422
25 nov. 2010 13:59:44 org.apache.solr.handler.dataimport.DocBuilder
collectDelta
INFO: Completed ModifiedRowKey for Entity: contrat rows obtained : 20
25 nov. 2010 13:59:44 org.apache.solr.handler.dataimport.DocBuilder
collectDelta
INFO: Completed DeletedRowKey for Entity: contrat rows obtained : 0
25 nov. 2010 13:59:44 org.apache.solr.handler.dataimport.DocBuilder
collectDelta
INFO: Completed parentDeltaQuery for Entity: contrat
25 nov. 2010 13:59:44 org.apache.solr.handler.dataimport.DocBuilder doDelta
INFO: Delta Import completed successfully
25 nov. 2010 13:59:44 org.apache.solr.handler.dataimport.DocBuilder execute
INFO: Time taken = 0:0:0.594

The import looks to be good, he found my changed documents, but none of this
documents were processed. Then i can't find my new documents in the index.

Do you have any idea on that point ?

Thanks
-- 
View this message in context: 
http://lucene.472066.n3.nabble.com/DIH-Delta-import-don-t-process-the-updated-documents-tp1966881p1966881.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: MoreLikeThis and two field in mlt.fl

[Jens Grivolla]

On 11/25/2010 10:06 AM, Damien Fontaine wrote:

I have a problem with MoreLikeThis on Solr 1.4.1. I can't put two field
on mlt.fl.
Example : text and title, only text is in interestingTerms


It should work. My guess is that the terms from the title simply don't 
make the cut due to mlt.mintf, which is often set so that only terms 
appearing multiple times are considered.


HTH,
Jens

About Solr Query help

[Himanshu Tatariya]

Hello,

Greetings !

I am working on one project which is used solr search facilities and its 
is good for searching and indexing it. I have one query regarding 
searching facets, so please guide me.


I search color just for example :

"*attr_color_sm:blue*" which i send in query but now I want put *"&& 
(AND)" and "|| (OR)"* condition in that query but I am not able to do this.
In that query I want pass another color like "Red" with both condition 
so please guide me for that.


Waiting for your reply. Thanks in advance.

Warm regards,
--
*Himanshu Tatariya*
Software Engineer,
Elan Technologies,
Software Development | IT Consulting
*ISO 9001:2008 Certified *| http://www.elantechnologies.com 




Disclaimer: Information transmitted/written in this e-mail is 
proprietary to elan emerging technologies pvt ltd and is intended for 
exclusive use by the individual or entity to which it is addressed by 
the sender (subject to his duties/delegation power) and may contain 
information that is privileged, confidential or exempt from disclosure 
under applicable law and shall not attach any liability on the 
originator. Any use, distribution, transmission, forwarding, printing, 
copying or dissemination of this information in any way or in any manner 
is strictly prohibited. All dispute if any are subject to the 
jurisdiction at the place where our company's registered office exists. 
If you have reason to believe that you are not the intended recipient of 
this communication, please contact the sender immediately. No 
responsibility whatsoever it may be for loss or damage arising from the 
use of the information transmitted by this email including damage from 
virus on elan emerging technologies pvt ltd.

Re: About Solr Query help

[Ahmet Arslan]

--- On Thu, 11/25/10, Himanshu Tatariya  wrote:

> From: Himanshu Tatariya 
> Subject: About Solr Query help
> To: solr-user@lucene.apache.org
> Date: Thursday, November 25, 2010, 4:02 PM
> Hello,
> 
> Greetings !
> 
> I am working on one project which is used solr search
> facilities and its is good for searching and indexing it. I
> have one query regarding searching facets, so please guide
> me.
> 
> I search color just for example :
> 
> "*attr_color_sm:blue*" which i send in query but now I want
> put *"&& (AND)" and "|| (OR)"* condition in that
> query but I am not able to do this.
> In that query I want pass another color like "Red" with
> both condition so please guide me for that.

What is not working?   Did you try this attr_color_sm:(blue || red) ?


  

Re: DisMaxQParserPlugin and Tokenization

[Jan Kurella]

Ok, I think I found it: the Queryparser used in the background "chunks" 
by whitespaces (and {}). Each of these chunks are then treated as 
"Phrases". This is complete useless for non-whitespace tokenizing languages.


So I started a simple DisMaxQueryParser. Can someone verify, that this 
codes produces a DisMaxQuery? (Theroy taken from here: 
http://www.lucidimagination.com/blog/2010/05/23/whats-a-dismax/)


{code}
stream = analyzer.reusableTokenStream("all", input);
TermAttribute oTermAtt = 
stream.addAttribute(TermAttribute.class);

int clauses = 0;
BooleanQuery result = new BooleanQuery();
while (stream.incrementToken()) {
DisjunctionMaxQuery clause = new DisjunctionMaxQuery(0.1f);
String oTermText = oTermAtt.term();
for (int iF = 0; iF < fields.length; ++iF) {
Query oQuery = new SpanTermQuery(new 
Term(fields[iF], oTermText));

clause.add(oQuery);
++clauses;
}
result.add(new BooleanClause(clause, Occur.SHOULD));
}
result.setMinimumNumberShouldMatch((int) Math.ceil(0.75* 
clauses)); // mm=75%

return result;
{code}

Is this, (basically, what the DisMaxQueryparser would do, if it would 
tokenize the full query without parsing for any of [+"{}] ?


Jan


On 24.11.2010 09:20, ext jan.kure...@nokia.com wrote:

Sorry for the double post. Is there someone, that can point me where the 
original query given to the DisMaxHandler/QParser is splitted?

Jan

-Original Message-
From: Kurella Jan (Nokia-MS/Berlin)
Sent: Montag, 22. November 2010 14:49
To: solr-user@lucene.apache.org
Subject: DisMaxQParserPlugin and Tokenization

Hi,

Using the SearchHandler with the deftype=”dismax” option enables the 
DisMaxQParserPlugin. From investigating it seems, it is just tokenizing by 
whitespace.

Although by looking in the code I could not find the place, where this behavior 
is enforced? I only found, that for each field the getFieldQuery() method is 
called, which either throws an “unknownField” exception or returns the correct 
analyzer including tokenizer and filter for the given field.

We want to use a more fancier Tokenizer/filter setting with the DisMaxQuery 
stuff.

Where to hook in best?

Jan

Re: Invoke directUpdateHandler2.deleteByQuery

[Erick Erickson]

I can think of two quick possibilities:
1> Just do a delete by query via XML, something like
specfield:value. You could use curl or put
it on the http request (separate from the delta import). There's an example
of posting via post.jar here: http://lucene.apache.org/solr/tutorial.html
curl example: curl http://localhost:8983/solr/update -F stream.body='your
query here'

2> WARNING: I haven't had occasion to use this, but did you look at
preImportDeleteQuery? See: http://wiki.apache.org/solr/DataImportHandler

Best
Erick

On Wed, Nov 24, 2010 at 11:31 PM, Robert Thayer
wrote:

> I am using DIH to load data from distinct locations and include a location
> specific field for faceting and hopefully deleting.  My current invocation
> of the DIH though, deletes all documents.
>
> After a little searching it looks like the proper config / invoke of the
> directUpdateHandler2.deleteByQuery() is what I'm looking but can't find any
> examples of how to do this.
>
> The best would be access at the request line, e.g.,
>
>
> ../solr/locationImport?command=full-import&deleteByQuery=locationField:location&..
>
> Or something like that.  Have already customized a transformer but this is
> after the fact of the delete.
>
> Any pointers are appreciated!
>
> Thanks
>

Re: SOLR 1.4.1 : Indexing DateField time zone problem

[Erick Erickson]

I don't believe this is a Solr issue at all. I suspect your MySql query is
doing the
timezone change. Solr doesn't apply any processing to the date, it doesn't
need to because times are all Zulu.

There's a little known debug console for DIH, see:
http://wiki.apache.org/solr/DataImportHandler#interactive
that might help a
lot. I think what you need to do is apply a transformation in your
SQL statement to get times in UTC, somthing like CONVERT_TZ or some such,
see:
http://dev.mysql.com/doc/refman/5.1/en/date-and-time-functions.html#function_convert-tz

Best
Erick

On Thu, Nov 25, 2010 at 5:27 AM, Shanmugavel SRD
wrote:

>
> I am using SOLR 1.4.1. My SOLR runs in a server which is in EST zone.
> I am trying to index a date field which is in MySQL as
> '2007-08-08T05:36:50Z' but while indexing it becomes '2007-08-08T09:36:50Z'
> where 4 hours got increased. But I want the date as is while indexing,
> means, after indexing I want the value as '2007-08-08T05:36:50Z' in
> 'modified_d' field.
>
> Can anyone help me on this?
>
>  dateTimeFormat="-MM-dd'T'hh:mm:ss'Z'" />
>
> I searched in this forum and there are discussions on this same problem but
> on SOLR 1.3, that's why I am posting this query again.
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/SOLR-1-4-1-Indexing-DateField-time-zone-problem-tp1966118p1966118.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>

Re: boosting

[Otis Gospodnetic]

Hi,

If a field always has a numeric value, does boosting it make any difference?  I 
never tested this explicitly, but assuming there is a single numerical token in 
a field, I'd think that field can either match or not match, so its 
contribution 
to the score will always have one of 2 possible values, depending on whether it 
matched or not.  If this is correct, then I'm not sure normalization matters 
here.

Otis

Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
Lucene ecosystem search :: http://search-lucene.com/



- Original Message 
> From: Gastone Penzo 
> To: solr-user@lucene.apache.org
> Sent: Wed, November 24, 2010 5:28:17 AM
> Subject: boosting
> 
> Hi,
> i have a problem/question to explain:
> 
> for example i have 3  documents with the same fields value, so the total
> score is the same for all  docs when i do a search
> that match.
> i have also some boosts set in bf  parameter (boost functions in dismax).
> 
> bf = field1^1.0 field2^0.8  field3^0.6
> 
> all the fields, except for 1, have values between 1 and 2 so i  can control
> the result score,
> but the field1 has unknown value (it can be  1 or 10).
> It is a problem cause i would like to normalize this in a range  between 1
> and 2 to compare score with the others.
> 
> is it possibile? if  not is there another way to do this??
> 
> Thank you
> 
> -- 
> Gastone  Penzo
> 

Re: SOLR 1.4.1 : Indexing DateField time zone problem

[Erik Fäßler]

Hm - but I observed this, too. And I didn't do anything with SQL at all. I was 
parsing date strings out of XML, creating a string which could be formatted 
using DIH's DateFormatTransformer. But the indexed dates have been a few hours 
too early in my case, switching back the dates to one day before. I didn't go 
deeply into this, I think I was experiencing a conversion of my dates strings 
from my time zone into UTC. My quick solution was to write another version of 
the DateFormatTransformer which takes a timeZone attribute. This way, the date 
strings shown in the indexed documents showed the correct date (which was what 
I wanted).
But I guess doing it this way also wasn't then best solution because when using 
date range math I ran into other time zone conversion problems, due to my own 
conversions earlier I think.

But until now I didn't go deeper into this so I don't know the exact reasons 
(although I'm sure it's not really a too challenging problem) and I haven't 
done a solution yet.

Best regards,

Erik


Am 25.11.2010 um 18:04 schrieb Erick Erickson :

> I don't believe this is a Solr issue at all. I suspect your MySql query is
> doing the
> timezone change. Solr doesn't apply any processing to the date, it doesn't
> need to because times are all Zulu.
> 
> There's a little known debug console for DIH, see:
> http://wiki.apache.org/solr/DataImportHandler#interactive
> that might help a
> lot. I think what you need to do is apply a transformation in your
> SQL statement to get times in UTC, somthing like CONVERT_TZ or some such,
> see:
> http://dev.mysql.com/doc/refman/5.1/en/date-and-time-functions.html#function_convert-tz
> 
> Best
> Erick
> 
> On Thu, Nov 25, 2010 at 5:27 AM, Shanmugavel SRD
> wrote:
> 
>> 
>> I am using SOLR 1.4.1. My SOLR runs in a server which is in EST zone.
>> I am trying to index a date field which is in MySQL as
>> '2007-08-08T05:36:50Z' but while indexing it becomes '2007-08-08T09:36:50Z'
>> where 4 hours got increased. But I want the date as is while indexing,
>> means, after indexing I want the value as '2007-08-08T05:36:50Z' in
>> 'modified_d' field.
>> 
>> Can anyone help me on this?
>> 
>> > dateTimeFormat="-MM-dd'T'hh:mm:ss'Z'" />
>> 
>> I searched in this forum and there are discussions on this same problem but
>> on SOLR 1.3, that's why I am posting this query again.
>> --
>> View this message in context:
>> http://lucene.472066.n3.nabble.com/SOLR-1-4-1-Indexing-DateField-time-zone-problem-tp1966118p1966118.html
>> Sent from the Solr - User mailing list archive at Nabble.com.
>> 

Using synonyms in combination with facets

[kirchheimer]

Hello,

I have a field that I use for facetting.  I do not tokenize this field. It
has entries like:

AWB artikel 2, lid 1
AWB artikel 8:75
Algemene Wet Bestuursrecht artikel 8:75

Now, I don't want to get hundreds of facets, but I would rather like to have
a facet for each law, instead for each pragraph of the law. I tried to do
this with a SynonymFilterFactory using rules like

Algemene Wet Bestuursrecht artikel 8:75 => AWB
AWB artikel 2, lid 1 => AWB

But that doesn't work. And even if it would work, it would not be a good
solution, since I will never be able to come up with a complete list, as
long as I cannot use wildcards.

What would be the right solution for this?


-- 
View this message in context: 
http://lucene.472066.n3.nabble.com/Using-synonyms-in-combination-with-facets-tp1968584p1968584.html
Sent from the Solr - User mailing list archive at Nabble.com.

Facet.query and collapsing

[Jean-Sebastien Vachon]

Hi All,

I'm in a situation where I need to perform a facet on a query with field 
collapsing.

Let's say the main query is something like this

title:apple&fq={!tag=sources}source_id:(33 OR 
44)&facet=on&facet.field={!ex=sources}source_id&facet.query=source_id:(33 OR 
44)&collapse=on&collapse.field=hash_id

I'd like my facet query to return the number of unique documents (based on the 
hash_id field) that are associated to either source 33 or 44

Right now, the query works but the count returned is larger than expected since 
there is no collapsing performed on the facet query's result set.

Is there any way of doing this? I'd like to be able to do this without 
performing a second request.

Thanks

NOTE: I'm using Solr 1.4.1 with patch 236 
(https://issues.apache.org/jira/browse/SOLR-236)