[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015722#comment-13015722
]
Yonik Seeley commented on SOLR-2444:
bq. you have seen SOLR-2443 right?
Heh - no I
[
https://issues.apache.org/jira/browse/LUCENE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015714#comment-13015714
]
Adriano Crestani commented on LUCENE-1768:
--
Hi Vinicius,
Your proposal looks go
[
https://issues.apache.org/jira/browse/LUCENE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015712#comment-13015712
]
Adriano Crestani commented on LUCENE-1768:
--
Hi Nikola,
That's great you are int
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015711#comment-13015711
]
Ryan McKinley commented on SOLR-2444:
-
you have seen SOLR-2443 right?
> Update fl
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015710#comment-13015710
]
Yonik Seeley commented on SOLR-2444:
FYI: just so we don't overlap effort, I'm busy add
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015681#comment-13015681
]
Yonik Seeley commented on SOLR-2444:
bq. This adds a parameter fl.pseudo=true/false – i
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015679#comment-13015679
]
Yonik Seeley edited comment on SOLR-2444 at 4/4/11 11:39 PM:
-
b
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015679#comment-13015679
]
Yonik Seeley commented on SOLR-2444:
bq. > What is the syntax of "argment"? is it backs
[
https://issues.apache.org/jira/browse/LUCENE-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015678#comment-13015678
]
Uwe Schindler commented on LUCENE-3014:
---
We should use the same code like Harmony h
[
https://issues.apache.org/jira/browse/LUCENE-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler reassigned LUCENE-3014:
-
Assignee: Uwe Schindler
> comparator API for segment versions
>
[
https://issues.apache.org/jira/browse/LUCENE-3012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3012:
Fix Version/s: (was: 3.1.1)
3.2
changing fix version to 3.2, especially giv
comparator API for segment versions
---
Key: LUCENE-3014
URL: https://issues.apache.org/jira/browse/LUCENE-3014
Project: Lucene - Java
Issue Type: Task
Reporter: Robert Muir
Priority: C
I wish Lucene query explanations were easier to localise
Key: LUCENE-3013
URL: https://issues.apache.org/jira/browse/LUCENE-3013
Project: Lucene - Java
Issue Type: Wish
Compo
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015673#comment-13015673
]
Ryan McKinley commented on SOLR-2444:
-
bq. It just seems both strange and limiting to s
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015667#comment-13015667
]
Ryan McKinley commented on SOLR-2444:
-
bq. but things now fail because of tests in trun
[
https://issues.apache.org/jira/browse/SOLR-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015663#comment-13015663
]
Yonik Seeley commented on SOLR-2456:
There's a lot of different things going on here.
[
https://issues.apache.org/jira/browse/SOLR-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-2456.
Resolution: Invalid
> Filter queries of values with + sign not decoded correctly
> -
Filter queries of values with + sign not decoded correctly
--
Key: SOLR-2456
URL: https://issues.apache.org/jira/browse/SOLR-2456
Project: Solr
Issue Type: Bug
Components: sea
[
https://issues.apache.org/jira/browse/SOLR-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015634#comment-13015634
]
Dawid Weiss commented on SOLR-2378:
---
The build time needs to sort the input again (and cr
[
https://issues.apache.org/jira/browse/SOLR-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015631#comment-13015631
]
Michael McCandless commented on SOLR-2378:
--
Wow those improvements are awesome --
On Apr 3, 2011, at 3:50 PM, Ryan McKinley wrote:
> In the days of sub-projects, I would have proposed that option, but
> now I see two options:
>
> A. Work on spatial lucene outside of apache -- perhaps osgeo or even
> just github. (would need a different name)
> B. Allow JTS compile-time depen
[
https://issues.apache.org/jira/browse/SOLR-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015627#comment-13015627
]
Dawid Weiss commented on SOLR-2378:
---
I'm done for the day. Lots of benchmarking and tweak
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015597#comment-13015597
]
Yonik Seeley commented on SOLR-2444:
bq. For the key use cases I can think of having a
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015593#comment-13015593
]
Yonik Seeley commented on SOLR-2444:
bq. [name] and [name:argument]
It just seems both
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015585#comment-13015585
]
Ryan McKinley commented on SOLR-2444:
-
bq. That seems like more complexity than it's wo
[
https://issues.apache.org/jira/browse/LUCENE-3012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3012:
Attachment: LUCENE-3012.patch
> if you use setNorm, lucene writes a headerless separate norms file
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015559#comment-13015559
]
Yonik Seeley edited comment on SOLR-2444 at 4/4/11 7:25 PM:
Hmm
if you use setNorm, lucene writes a headerless separate norms file
--
Key: LUCENE-3012
URL: https://issues.apache.org/jira/browse/LUCENE-3012
Project: Lucene - Java
Issue Type:
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015559#comment-13015559
]
Yonik Seeley commented on SOLR-2444:
Hmmm, I've tried changing '=' to ':' for the key..
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015554#comment-13015554
]
Yonik Seeley commented on SOLR-2444:
bq. I don't think we can treat the pseudo fields a
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015551#comment-13015551
]
Ryan McKinley commented on SOLR-2444:
-
bq, For user directly asking for functions, we'l
[
https://issues.apache.org/jira/browse/SOLR-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015537#comment-13015537
]
Otis Gospodnetic commented on SOLR-1853:
This issue is still open, but it looks lik
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015531#comment-13015531
]
Yonik Seeley commented on SOLR-2444:
Ok, so it seems like we're agreeing on two differe
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015522#comment-13015522
]
Ryan McKinley commented on SOLR-2444:
-
Thinking about the pseudo field mapping -- I lik
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015515#comment-13015515
]
Yonik Seeley commented on SOLR-2444:
>From the high level user perspective, a field and
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015509#comment-13015509
]
Ryan McKinley commented on SOLR-2444:
-
Erik -- so you are suggesting that the fl list i
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015502#comment-13015502
]
Erik Hatcher commented on SOLR-2444:
I'm kinda liking having fl stay unadorned, such th
: with category and prices. We definitely want to show off more advanced
: features, and we should add more example documents for that. Plain test
: docs could be placed in a a subfolder "exampledocs/extras" or something.
+1
or "exampledocs/exotic" or "exampledocs/complex"
-Hoss
---
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015495#comment-13015495
]
Hoss Man commented on SOLR-2444:
bq. I like the syntax you suggest. The reason i suggested
>From my tests, this only affects Windows XP and previous.
*Nix and OSX use always full charset.jar. Windows Vista and Windows 7 by
default "support" all languages and report this back through
http://msdn.microsoft.com/en-us/library/dd317827(v=vs.85).aspx , so the
"testing code" in the installer g
We don't have any sort of QA report on the latest build. DIGY called
for testing, but I haven't seen anyone respond to that request
indicating successful testing.
So, how do we want to manage this?
In the business world, we'd never think of making a release without
extensive QA first. In my other
Makes sense.
Question is, do we want to require full JDK to index exampledocs? Most
developers will have a JDK, but the occasional semi-tech manager just wanting
to test out Solr may get burnt and think "Open Source sucks, just as I thought"
:)
I added a note to http://wiki.apache.org/solr/Sol
Hi Patrick,
This may or may not be helpful for your requirements, but there is a
new, somewhat related patch for case-insensitive wildcard queries:
It's in: https://issues.apache.org/jira/browse/SOLR-2438
HTH,
Peter
On Mon, Apr 4, 2011 at 10:43 AM, Patrick Allaert (JIRA) wrote:
>
> [
> ht
[
https://issues.apache.org/jira/browse/SOLR-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey Chang updated SOLR-2455:
Attachment: SOLR-2455.patch
> admin/index.jsp double submit on IE
>
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/6711/
1 tests failed.
REGRESSION: org.apache.lucene.collation.TestCollationKeyAnalyzer.testThreadSafe
Error Message:
Java heap space
Stack Trace:
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf
[
https://issues.apache.org/jira/browse/SOLR-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey Chang updated SOLR-2455:
Description:
/admin/index.jsp could issue a double submit on IE causing Jetty to error out.
Here ar
admin/index.jsp double submit on IE
---
Key: SOLR-2455
URL: https://issues.apache.org/jira/browse/SOLR-2455
Project: Solr
Issue Type: Bug
Affects Versions: 3.1
Environment: IE8
Reporte
To come back to the original issue:
If you are using a pure JRE installed in your operating system using the
standard mechanism "browser automatically installs Java Plugin methods" or
similar, the following applies:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6329080
To reduce size of downl
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015447#comment-13015447
]
Ryan McKinley commented on SOLR-2444:
-
bq. but perhaps we should get feedback from more
[
https://issues.apache.org/jira/browse/SOLR-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015441#comment-13015441
]
Mark Miller commented on SOLR-2193:
---
bq. I'll upload a patch after I start lazy creating
[
https://issues.apache.org/jira/browse/SOLR-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015440#comment-13015440
]
Simon Willnauer commented on SOLR-2193:
---
bq. I've updated my patch to trunk.
hmm may
[
https://issues.apache.org/jira/browse/LUCENE-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015434#comment-13015434
]
Dawid Weiss commented on LUCENE-3011:
-
Yes, it does -- thanks Robert. I will provide
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015432#comment-13015432
]
Yonik Seeley commented on SOLR-2444:
bq. There is also no way to implement the quoted f
[
https://issues.apache.org/jira/browse/SOLR-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015415#comment-13015415
]
Fuad Efendi commented on SOLR-792:
--
Hi,
Jason Folk posted:
bq. facet.tree currently seems
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015413#comment-13015413
]
Ryan McKinley commented on SOLR-2444:
-
got it -- yes, this first splits on comma -- so
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015410#comment-13015410
]
Yonik Seeley commented on SOLR-2444:
bq. The stuff i did (in the branch), still uses th
[
https://issues.apache.org/jira/browse/LUCENE-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3011:
Attachment: LUCENE-3011.patch
Dawid: does this help?
> Add serialization/deserialization of FST i
Would like link in site navigation to the ManifoldCF project
Key: SOLR-2454
URL: https://issues.apache.org/jira/browse/SOLR-2454
Project: Solr
Issue Type: Improvement
Com
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015397#comment-13015397
]
Ryan McKinley commented on SOLR-2444:
-
i'm not suggesting the StringTokenizer approach
[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015393#comment-13015393
]
Yonik Seeley commented on SOLR-2444:
bq. i replaced your fancy parsing with something i
[
https://issues.apache.org/jira/browse/LUCENE-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015391#comment-13015391
]
Robert Muir commented on LUCENE-3011:
-
But it doesn't really use it right? its just a
Solr should not wrap TokenStreams in a caching filter when using
usePhraseHighlighter=true
--
Key: SOLR-2453
URL: https://issues.apache.org/jira/browse/SOLR-2453
[
https://issues.apache.org/jira/browse/LUCENE-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved LUCENE-2951.
-
Resolution: Invalid
wrong project
> Solr should not wrap TokenStreams in a caching filter when
[
https://issues.apache.org/jira/browse/LUCENE-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015382#comment-13015382
]
Dawid Weiss commented on LUCENE-3011:
-
I tried that before, but CodecUtil.writeHeader
On Mon, Apr 4, 2011 at 7:51 AM, Uwe Schindler wrote:
> Hi Jan,
>
>> Regarding the WindowsXP VMmware I was using, it had a Sun JRE (not JDK)
>> which was auto-updated from 1.5 to 1.6.
>> After completely uninstalling Java and re-installing jdk-6u24-windows-
>> i586.exe the GB18030 encoding is suppo
[
https://issues.apache.org/jira/browse/LUCENE-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015374#comment-13015374
]
Michael McCandless commented on LUCENE-3011:
+1
Maybe one way to do this is
Hi Jan,
> Regarding the WindowsXP VMmware I was using, it had a Sun JRE (not JDK)
> which was auto-updated from 1.5 to 1.6.
> After completely uninstalling Java and re-installing jdk-6u24-windows-
> i586.exe the GB18030 encoding is supported.
Just out of curiosity: A JRE-only configuration should
Add serialization/deserialization of FST instances from plain
InputStream/OutputStream.
---
Key: LUCENE-3011
URL: https://issues.apache.org/jira/browse/LUCENE-3011
Pr
No, it's a single file, but the only way to serialize it is via
IndexOutput/IndexInput and these require a Directory. I'll switch to
using a subfolder, but this use case makes me think a simple
serializer/deserializer from InputStream/OutputStream would be
probably a good addition to the automaton
On 4/4/11 1:26 PM, Dawid Weiss wrote:
Yeah, I know, but you create a subfile in that folder and in case of
FSDirectory a subfolder would be created for the automaton... so for
'parent' you'd have something like:
parent/fstlookup/fst.file
Can it look this way or is:
parent/fst.file
more suitab
>>> : I don't see the reason why "exampledocs" should contain docs with narrow
>>> charsets not guaranteed to be supported.
>> personally i would like to see us add a lot more exampledocs in a lot more
>> esoteric encodings, precisely to help end users sanity test this sort of
>> we frequetnly get
Yeah, I know, but you create a subfile in that folder and in case of
FSDirectory a subfolder would be created for the automaton... so for
'parent' you'd have something like:
parent/fstlookup/fst.file
Can it look this way or is:
parent/fst.file
more suitable? This is most likely a matter of tast
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/6712/
1 tests failed.
REGRESSION: org.apache.solr.cloud.CloudStateUpdateTest.testCoreRegistration
Error Message:
null
Stack Trace:
junit.framework.AssertionFailedError:
at
org.apache.lucene.util.LuceneTestCase$Lu
[
https://issues.apache.org/jira/browse/SOLR-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015333#comment-13015333
]
Patrick Allaert commented on SOLR-219:
--
Any plan to implement this?
> Determine if pre
On 4/4/11 11:29 AM, Dawid Weiss wrote:
Hi guys. FST currently uses IndexInput/IndexOutput to perform
serialization and the suggester framework expects a single file. Is
there any nice way to do this? I ask because I considered these, but
they all seem clumsy:
a) serialize suggester data to a sub
Hi guys. FST currently uses IndexInput/IndexOutput to perform
serialization and the suggester framework expects a single file. Is
there any nice way to do this? I ask because I considered these, but
they all seem clumsy:
a) serialize suggester data to a subfolder (using regular
FSDirectory); this
Build: https://hudson.apache.org/hudson/job/Solr-trunk/1464/
All tests passed
Build Log (for compile errors):
[...truncated 22695 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e
[
https://issues.apache.org/jira/browse/SOLR-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015305#comment-13015305
]
Dawid Weiss commented on SOLR-2378:
---
Thanks Ryan. Well, I'll just allocate off the heap,
78 matches
Mail list logo
