[
https://issues.apache.org/jira/browse/SOLR-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494918
]
Ian Holsman commented on SOLR-232:
--
Hi Otis.
The UI would be a generic monitoring tool similar to
http://pyro.holsma
On 10-May-07, at 4:46 PM, Ryan McKinley wrote:
Otis Gospodnetic wrote:
I haven't moved to 6.* yet. But I did notice 6.1.3 showed up a
few days ago.
I think 6.1.3 showed up a day after 6.1.2!
That's always an encouraging sign :)
-Mike
Otis Gospodnetic wrote:
I haven't moved to 6.* yet. But I did notice 6.1.3 showed up a few days ago.
I think 6.1.3 showed up a day after 6.1.2!
I just posted a jar with the contents of /example on
https://issues.apache.org/jira/browse/SOLR-128
I'm only using it for very simple things, but i
[
https://issues.apache.org/jira/browse/SOLR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-128:
---
Attachment: jetty-6.3-example.zip
here is a zip with the example directory as we would (maybe) want it.
I haven't moved to 6.* yet. But I did notice 6.1.3 showed up a few days ago.
Otis
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Simpy -- http://www.simpy.com/ - Tag - Search - Share
- Original Message
From: Yonik Seeley <[EMAIL PROTECTED]>
To: solr-dev@lucene.apache
[
https://issues.apache.org/jira/browse/SOLR-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494899
]
Otis Gospodnetic commented on SOLR-232:
---
Interesting. Does it have a UI piece? Do you need that "start" variabl
[
https://issues.apache.org/jira/browse/SOLR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-225:
---
Attachment: SOLR-225-HighlightingConfig.patch
no real changes... it applies cleanly with trunk.
> The
[
https://issues.apache.org/jira/browse/SOLR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-231.
Resolution: Fixed
added in 537024
> By default, use UTF-8 for posted content streams
> -
[
https://issues.apache.org/jira/browse/SOLR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-231:
--
Assignee: Ryan McKinley
> By default, use UTF-8 for posted content streams
>
On 10-May-07, at 3:02 PM, Daniel Creão wrote:
So, I tried Solr and read about FederatedSearch and
CollectionDistribution.
An 'all-machines-have-complete-index' strategy (using rsync) can
improve
system throughput and concurrency by each station processing different
queries, but each query wil
[
https://issues.apache.org/jira/browse/SOLR-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-226.
Resolution: Fixed
Fix Version/s: (was: 1.3)
1.2
added in rev 536730
>
[
https://issues.apache.org/jira/browse/SOLR-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-224.
Resolution: Fixed
in rev 537014
> PhoneticFilterFactory -- support Metaphone/Soundex filters
> -
I'm looking forward some strategy to build a large Lucene distributed index,
but after read a lot of mail threads, it seems that Lucene hasn't a 'default
solution' for that yet.
The search engine that I'm building has a 400 GB text-database (right now,
growing every day and without document delet
[
https://issues.apache.org/jira/browse/SOLR-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-224:
--
Assignee: Ryan McKinley
> PhoneticFilterFactory -- support Metaphone/Soundex filters
> --
[
https://issues.apache.org/jira/browse/SOLR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-233.
Resolution: Fixed
changed the example.xls to have:
in rev 537004
> Add UTF-8 support to exampl
[
https://issues.apache.org/jira/browse/SOLR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley reassigned SOLR-233:
--
Assignee: Ryan McKinley
> Add UTF-8 support to example.xsl
>
>
>
Emmanuel,
This sounds useful!
Here is everything you'll need to know:
http://wiki.apache.org/solr/HowToContribute
Thanks,
Otis
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Simpy -- http://www.simpy.com/ - Tag - Search - Share
- Original Message
From: Emmanuel Kell
Add UTF-8 support to example.xsl
Key: SOLR-233
URL: https://issues.apache.org/jira/browse/SOLR-233
Project: Solr
Issue Type: Bug
Components: search
Affects Versions: 1.1.0
Environment:
Hi,
My name is Emmanuel Keller. I am an engineer working as technical manager
for a french company.
For some projects, I identified that Lucene was the search engine we need.
I worked hard to successfully integrate Solr on the first project:
http://www.usinenouvelle.com/expo
For the next projec
: Thanks, I should have checked the wiki.
it's also called out in the "Upgrading from Solr 1.1" section of the
CHANGES.txt file...
http://svn.apache.org/repos/asf/lucene/solr/trunk/CHANGES.txt
...
The JSON response format for facets has changed to make it easier for
clients to retain sorted orde
The ever growing presence of mingled structured and unstructured data is a
fact of life and modern systems we have to deal with. Clearly, the tendency
is that full-text indexing is moving towards DB functionality, i.e.
fields for projection/filtering, sorting, faceted queries,
transactional CRUD
Thanks, I should have checked the wiki.
Cheers,
Andrew
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yonik
Seeley
Sent: Thursday, May 10, 2007 9:32 AM
To: solr-dev@lucene.apache.org
Subject: Re: bug in JSON Response
On 5/10/07, Gunther, Andrew <[EMAIL P
On 5/10/07, Gunther, Andrew <[EMAIL PROTECTED]> wrote:
Anyone notice an error in the JSON response when requesting facets.
The response I get is:
{"facet_queries":{},"facet_fields":{"subject":["Landscape",10335,"River"
,1767,"Mountain",1278,"Architecture",1184] }}
It seems like the JSONArray su
Anyone notice an error in the JSON response when requesting facets.
The response I get is:
{"facet_queries":{},"facet_fields":{"subject":["Landscape",10335,"River"
,1767,"Mountain",1278,"Architecture",1184] }}
It seems like the JSONArray subject should yield a JSONObject with
name,value pairs lik
24 matches
Mail list logo
