New interface PluginInfoInitialized
---
Key: SOLR-1326
URL: https://issues.apache.org/jira/browse/SOLR-1326
Project: Solr
Issue Type: Improvement
Reporter: Noble Paul
There is no way for a
In my quest to improve indexing time (in a multi-core environment), I tried
writing a Solr RequestHandler called ParallelDataImportHandler.
I had a few lame questions to begin with, which Noble and Shalin answered
here -
a multithreaded DIH is in my top priority list. There are muliple approaches
1) create multiple instances of dataImporter instances in the same DIH
instance and run them in parallel and commit when all of them are done
2) run the add() calls to Solr in a dedicated thread
3) make DIH automatically
run the add() calls to Solr in a dedicated thread
Makes absolute sense. This would actually mean, DIH sits on top of all the
add/update operations making it easier to implement a multi-threaded DIH.
I would create a JIRA issue, right away.
However, I would still love to see responses to my
I have one more question w.r.t the MultiThreaded DIH - What would be the
logic behind distributing tasks to thread?
I am sorry to have not mentioned this earlier - In my case, I take a count
query parameter as an configuration element. Based on this count and the
maxNumberOfDIHInstances, task
Allow special Filters to access, modify, and/or add Fields to/on a Solr Document
Key: SOLR-1327
URL: https://issues.apache.org/jira/browse/SOLR-1327
Project: Solr
On Sun, Aug 2, 2009 at 8:56 PM, Avlesh Singhavl...@gmail.com wrote:
I have one more question w.r.t the MultiThreaded DIH - What would be the
logic behind distributing tasks to thread?
I am sorry to have not mentioned this earlier - In my case, I take a count
query parameter as an
There can be a batch command (which) will take in multiple commands in one
http request.
You seem to be obsessed with this approach, Noble.
Solr-1093http://issues.apache.org/jira/browse/SOLR-1093also echoes
the same sentiments :)
I personally find this approach a bit restrictive and difficult
implement date faceting for trie date
-
Key: SOLR-1328
URL: https://issues.apache.org/jira/browse/SOLR-1328
Project: Solr
Issue Type: Sub-task
Affects Versions: 1.4
Reporter: Yonik Seeley
[
https://issues.apache.org/jira/browse/SOLR-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-1089:
-
Attachment: SOLR-1089.patch
do write to Solr in a separate thread
-
I'm working on a jumbo trie patch (just many smaller trie related
issues at once) - SOLR-1288.
Anyway, I think support will be good enough for 1.4 that we should
make types like integer in the example schema be based on the trie
fields. The current integer fields should be renamed to pinteger
[
https://issues.apache.org/jira/browse/SOLR-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul reassigned SOLR-1089:
Assignee: Noble Paul
do write to Solr in a separate thread
-
StatsComponent needs trie support
-
Key: SOLR-1329
URL: https://issues.apache.org/jira/browse/SOLR-1329
Project: Solr
Issue Type: Bug
Affects Versions: 1.4
Reporter: Yonik Seeley
Currently,
Would it make sense to instead add new tint(eger) type instead of renaming
integer to pinteger? (thinking about people upgrading to Solr 1.4).
Otis
--
Sematext is hiring -- http://sematext.com/about/jobs.html?mls
Lucene, Solr, Nutch, Katta, Hadoop, HBase, UIMA, NLP, NER, IR
- Original
the details command shows current replication status when no replication is
going on
Key: SOLR-1330
URL: https://issues.apache.org/jira/browse/SOLR-1330
Project:
[
https://issues.apache.org/jira/browse/SOLR-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul reassigned SOLR-1330:
Assignee: Noble Paul
the details command shows current replication status when no replication is
[
https://issues.apache.org/jira/browse/SOLR-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-1330:
-
Attachment: SOLR-1330.patch
the details command shows current replication status when no replication is
[
https://issues.apache.org/jira/browse/SOLR-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-1330:
-
Attachment: SOLR-1330.patch
also keep at least 10 latest timestamps of replication
the details command
[
https://issues.apache.org/jira/browse/SOLR-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-1330:
-
Attachment: (was: SOLR-1330.patch)
the details command shows current replication status when no
[
https://issues.apache.org/jira/browse/SOLR-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-1330:
-
Attachment: SOLR-1330.patch
the details command shows current replication status when no replication is
20 matches
Mail list logo
