[jira] Updated: (SOLR-670) UpdateHandler must provide a rollback feature
[
https://issues.apache.org/jira/browse/SOLR-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Sekiguchi updated SOLR-670:
Attachment: SOLR-670.patch
Updated patch which includes commit and rollback test. The test looks like:
{code:title=pseudo code}
public void testUncommit() throws Exception {
add(doc(A));
search(A); // A should not be found.
}
public void testAddCommit() throws Exception {
add(doc(A));
commit();
search(A); // A should be found.
}
public void testDeleteCommit() throws Exception {
add(doc(A));
add(doc(B));
commit();
search(A OR B); // A and B should be found.
delete(doc(B));
search(A OR B); // A and B should be found.
commit();
search(A OR B); // B should not be found.
}
public void testAddRollback() throws Exception {
add(doc(A));
commit();
add(doc(B));
rollback();
commit();
search(A OR B); // B should not be found.
}
public void testDeleteRollback() throws Exception {
add(doc(A));
add(doc(B));
commit();
search(A OR B); // A and B should be found.
delete(doc(B));
rollback();
commit();
search(A OR B); // A and B should be found.
}
{code}
UpdateHandler must provide a rollback feature
-
Key: SOLR-670
URL: https://issues.apache.org/jira/browse/SOLR-670
Project: Solr
Issue Type: New Feature
Components: search
Affects Versions: 1.3
Reporter: Noble Paul
Assignee: Shalin Shekhar Mangar
Fix For: 1.4
Attachments: SOLR-670.patch, SOLR-670.patch
Lucene IndexWriter already has a rollback method. There should be a
counterpart for the same in _UpdateHandler_ so that users can do a rollback
over http
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-802) Trivial bug which could cause null pointer exception
[ https://issues.apache.org/jira/browse/SOLR-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12637595#action_12637595 ] Jayson Minard commented on SOLR-802: Thanks David! And Ryan, can the title be adjusted to indicate where and when this could happen so that release notes are more obvious? Trivial bug which could cause null pointer exception Key: SOLR-802 URL: https://issues.apache.org/jira/browse/SOLR-802 Project: Solr Issue Type: Bug Components: search Affects Versions: 1.3 Reporter: David Bowen Assignee: Ryan McKinley Priority: Minor Attachments: patch In FacetComponent there's an which should be a . Patch to follow. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-802) Trivial bug in distributed FacetComponent code that could cause null pointer exception
[ https://issues.apache.org/jira/browse/SOLR-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley updated SOLR-802: --- Summary: Trivial bug in distributed FacetComponent code that could cause null pointer exception (was: Trivial bug which could cause null pointer exception) Trivial bug in distributed FacetComponent code that could cause null pointer exception -- Key: SOLR-802 URL: https://issues.apache.org/jira/browse/SOLR-802 Project: Solr Issue Type: Bug Components: search Affects Versions: 1.3 Reporter: David Bowen Assignee: Ryan McKinley Priority: Minor Attachments: patch In FacetComponent there's an which should be a . Patch to follow. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-739) Add support for OmitTf
[ https://issues.apache.org/jira/browse/SOLR-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12637612#action_12637612 ] Mark Miller commented on SOLR-739: -- So whats the verdict...leave as is, or should I tick the schema version? Add support for OmitTf -- Key: SOLR-739 URL: https://issues.apache.org/jira/browse/SOLR-739 Project: Solr Issue Type: New Feature Reporter: Mark Miller Priority: Minor Fix For: 1.4 Attachments: SOLR-739.patch Allow setting omitTf in the field schema. Default to true for all but text fields. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-799) Add support for hash based exact/near duplicate document handling
[ https://issues.apache.org/jira/browse/SOLR-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-799: - Attachment: SOLR-799.patch First pass for comments/reaction Add support for hash based exact/near duplicate document handling - Key: SOLR-799 URL: https://issues.apache.org/jira/browse/SOLR-799 Project: Solr Issue Type: New Feature Components: update Reporter: Mark Miller Priority: Minor Attachments: SOLR-799.patch Hash based duplicate document detection is efficient and allows for blocking as well as field collapsing. Lets put it into solr. http://wiki.apache.org/solr/Deduplication -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-465) Add configurable DirectoryProvider so that alternate Directory implementations can be specified via solrconfig.xml
[ https://issues.apache.org/jira/browse/SOLR-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12637633#action_12637633 ] Mark Miller commented on SOLR-465: -- I've worked a bit on updating this to trunk, but it has a bit of overlap with solr-243, so if either are going in, it will be much easier to finish the other after. Add configurable DirectoryProvider so that alternate Directory implementations can be specified via solrconfig.xml -- Key: SOLR-465 URL: https://issues.apache.org/jira/browse/SOLR-465 Project: Solr Issue Type: New Feature Affects Versions: 1.3 Reporter: TJ Laurenzo Fix For: 1.4 Attachments: SOLR-465.patch, solr-directory-provider.patch Original Estimate: 0.25h Remaining Estimate: 0.25h Solr is presently hard-coded to use the FSDirectory implementation in Lucene. Other Directory implementations are possible. This patch creates a new DirectoryProvider interface and extends SolrCore to load an implementation of it from solrconfig.xml (if specified). If not specified, then it will fallback to the FSDirectory. A DirectoryProvider plugin can be configured in solrconfig.xml with the following XML: directoryProvider class=class.name !-- Parameters as required by the implementation -- /directoryProvider This patch was created against solr trunk checked out on 11/20/2007. Most of it is new code and should apply cleanly or with minor relocation. If it does not, let me know and I will update. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-799) Add support for hash based exact/near duplicate document handling
[ https://issues.apache.org/jira/browse/SOLR-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12637649#action_12637649 ] Andrzej Bialecki commented on SOLR-799: Interesting development in light of NUTCH-442 :) Some comments: * in MD5Signature I suggest using the code from org.apache.hadoop.io.MD5Hash.toString() instead of BigInteger. * TextProfileSignature should contain a remark that it's copied from Nutch, since AFAIK the algorithm that it implements is currently used only in Nutch. * in Nutch the concept of a page Signature is only a part of the deduplication process. The other part is the algorithm to decide which copy to keep and which one to discard. In your patch the latest update always removes all other documents with the same signature. IMHO this decision should be isolated into a DuplicateDeletePolicy class that gets all duplicates and can decide (based on arbitrary criteria) which one to keep, with the default implementation that simply keeps the latest document. Add support for hash based exact/near duplicate document handling - Key: SOLR-799 URL: https://issues.apache.org/jira/browse/SOLR-799 Project: Solr Issue Type: New Feature Components: update Reporter: Mark Miller Priority: Minor Attachments: SOLR-799.patch Hash based duplicate document detection is efficient and allows for blocking as well as field collapsing. Lets put it into solr. http://wiki.apache.org/solr/Deduplication -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-243) Create a hook to allow custom code to create custom IndexReaders
[
https://issues.apache.org/jira/browse/SOLR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-243:
-
Attachment: SOLR-243.patch
Adds a config option to turn on/off reopening readers. apache pork.
Create a hook to allow custom code to create custom IndexReaders
Key: SOLR-243
URL: https://issues.apache.org/jira/browse/SOLR-243
Project: Solr
Issue Type: Improvement
Components: search
Environment: Solr core
Reporter: John Wang
Assignee: Hoss Man
Fix For: 1.4
Attachments: indexReaderFactory.patch, indexReaderFactory.patch,
indexReaderFactory.patch, indexReaderFactory.patch, indexReaderFactory.patch,
indexReaderFactory.patch, indexReaderFactory.patch, SOLR-243.patch,
SOLR-243.patch, SOLR-243.patch
I have a customized IndexReader and I want to write a Solr plugin to use my
derived IndexReader implementation. Currently IndexReader instantiation is
hard coded to be:
IndexReader.open(path)
It would be really useful if this is done thru a plugable factory that can be
configured, e.g. IndexReaderFactory
interface IndexReaderFactory{
IndexReader newReader(String name,String path);
}
the default implementation would just return: IndexReader.open(path)
And in the newSearcher and getSearcher methods in SolrCore class can call the
current factory implementation to get the IndexReader instance and then build
the SolrIndexSearcher by passing in the reader.
It would be really nice to add this improvement soon (This seems to be a
trivial addition) as our project really depends on this.
Thanks
-John
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-84) New Solr logo?
[ https://issues.apache.org/jira/browse/SOLR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Vlcek updated SOLR-84: Attachment: solr_logo_it_is_burning.png It is burning! ... Apache Solr Logo contest submition (based on my previous draft http://picasaweb.google.cz/lukas.vlcek/Solr) New Solr logo? -- Key: SOLR-84 URL: https://issues.apache.org/jira/browse/SOLR-84 Project: Solr Issue Type: Improvement Reporter: Bertrand Delacretaz Priority: Minor Attachments: logo-grid.jpg, logo-solr-d.jpg, logo-solr-e.jpg, logo-solr-source-files-take2.zip, solr-84-source-files.zip, solr-f.jpg, solr-logo-20061214.jpg, solr-logo-20061218.JPG, solr-logo-20070124.JPG, solr-nick.gif, solr.jpg, solr.s1.jpg, solr.svg, solr_logo_it_is_burning.png, sslogo-solr-flare.jpg, sslogo-solr.jpg, sslogo-solr2-flare.jpg, sslogo-solr2.jpg, sslogo-solr3.jpg Following up on SOLR-76, our trainee Nicolas Barbay (nicolas (put at here) sarraux-dessous.ch) has reworked his logo proposal to be more solar. This can either be the start of a logo contest, or if people like it we could adopt it. The gradients can make it a bit hard to integrate, not sure if this is really a problem. WDYT? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-799) Add support for hash based exact/near duplicate document handling
[ https://issues.apache.org/jira/browse/SOLR-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12637719#action_12637719 ] Mark Miller commented on SOLR-799: -- Thanks for the review Andrzej. I've made the first two changes (I put at the top of TextProfileSignature that its 'borrowed' from Nutch and grabbed Hadoops MD5Hash class and stripped its Hadoop dependencies) and I'm investigating change 3. I'll put up another patch in a couple days. - Mark Add support for hash based exact/near duplicate document handling - Key: SOLR-799 URL: https://issues.apache.org/jira/browse/SOLR-799 Project: Solr Issue Type: New Feature Components: update Reporter: Mark Miller Priority: Minor Attachments: SOLR-799.patch Hash based duplicate document detection is efficient and allows for blocking as well as field collapsing. Lets put it into solr. http://wiki.apache.org/solr/Deduplication -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Updated: (SOLR-84) New Solr logo?
do we really need the APACHE under the solr logo? the other one looks clean On Wed, Oct 8, 2008 at 4:22 AM, Lukas Vlcek (JIRA) [EMAIL PROTECTED] wrote: [ https://issues.apache.org/jira/browse/SOLR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Vlcek updated SOLR-84: Attachment: solr_logo_it_is_burning.png It is burning! ... Apache Solr Logo contest submition (based on my previous draft http://picasaweb.google.cz/lukas.vlcek/Solr) New Solr logo? -- Key: SOLR-84 URL: https://issues.apache.org/jira/browse/SOLR-84 Project: Solr Issue Type: Improvement Reporter: Bertrand Delacretaz Priority: Minor Attachments: logo-grid.jpg, logo-solr-d.jpg, logo-solr-e.jpg, logo-solr-source-files-take2.zip, solr-84-source-files.zip, solr-f.jpg, solr-logo-20061214.jpg, solr-logo-20061218.JPG, solr-logo-20070124.JPG, solr-nick.gif, solr.jpg, solr.s1.jpg, solr.svg, solr_logo_it_is_burning.png, sslogo-solr-flare.jpg, sslogo-solr.jpg, sslogo-solr2-flare.jpg, sslogo-solr2.jpg, sslogo-solr3.jpg Following up on SOLR-76, our trainee Nicolas Barbay (nicolas (put at here) sarraux-dessous.ch) has reworked his logo proposal to be more solar. This can either be the start of a logo contest, or if people like it we could adopt it. The gradients can make it a bit hard to integrate, not sure if this is really a problem. WDYT? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. -- --Noble Paul
Re: [jira] Updated: (SOLR-84) New Solr logo?
It seems so, according to official requiremetns: http://wiki.apache.org/solr/LogoContest On Wed, Oct 8, 2008 at 6:44 AM, Noble Paul നോബിള് नोब्ळ् [EMAIL PROTECTED] wrote: do we really need the APACHE under the solr logo? the other one looks clean On Wed, Oct 8, 2008 at 4:22 AM, Lukas Vlcek (JIRA) [EMAIL PROTECTED] wrote: [ https://issues.apache.org/jira/browse/SOLR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] Lukas Vlcek updated SOLR-84: Attachment: solr_logo_it_is_burning.png It is burning! ... Apache Solr Logo contest submition (based on my previous draft http://picasaweb.google.cz/lukas.vlcek/Solr) New Solr logo? -- Key: SOLR-84 URL: https://issues.apache.org/jira/browse/SOLR-84 Project: Solr Issue Type: Improvement Reporter: Bertrand Delacretaz Priority: Minor Attachments: logo-grid.jpg, logo-solr-d.jpg, logo-solr-e.jpg, logo-solr-source-files-take2.zip, solr-84-source-files.zip, solr-f.jpg, solr-logo-20061214.jpg, solr-logo-20061218.JPG, solr-logo-20070124.JPG, solr-nick.gif, solr.jpg, solr.s1.jpg, solr.svg, solr_logo_it_is_burning.png, sslogo-solr-flare.jpg, sslogo-solr.jpg, sslogo-solr2-flare.jpg, sslogo-solr2.jpg, sslogo-solr3.jpg Following up on SOLR-76, our trainee Nicolas Barbay (nicolas (put at here) sarraux-dessous.ch) has reworked his logo proposal to be more solar. This can either be the start of a logo contest, or if people like it we could adopt it. The gradients can make it a bit hard to integrate, not sure if this is really a problem. WDYT? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. -- --Noble Paul -- http://blog.lukas-vlcek.com/
[jira] Issue Comment Edited: (SOLR-84) New Solr logo?
[ https://issues.apache.org/jira/browse/SOLR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12636849#action_12636849 ] solprovider edited comment on SOLR-84 at 10/7/08 10:21 PM: --- Attached solr.s1.jpg -- variation of logo-solr-d.jpg, the white center of the O allows resizing smaller without using red. Concept is consistent height and thinner S. Used capital L to avoid confusion with I vowel. Kept the lowercase R; a capital R destroys the simplicity. I like the rounded corners, although they disappear at smaller sizes. (Use half-circles for all ends?) Logo must include Apache. Added as white text inside the S. Disappears at smaller sizes so we may need two versions to meet this requirement at small sizes. Solr is for the enterprise and needs a logo acceptable to large companies. IMO, none of the logos with flames meet this standard. was (Author: solprovider): Attached variation of logo-solr-d.jpg (currently #2.) The white center of the O allows resizing smaller without using red. Concept is consistent height and thinner S. Used capital L to avoid confusion with I vowel. Kept the lowercase R. I like the rounded corners, although they disappear at smaller sizes. Logo must include Apache. Added as white text inside the S. Disappears at smaller sizes so we may need two versions to meet this requirement at small sizes. Soly is for the enterprise and needs a logo acceptable to large companies. IMO, none of the logos with flames meet this standard. New Solr logo? -- Key: SOLR-84 URL: https://issues.apache.org/jira/browse/SOLR-84 Project: Solr Issue Type: Improvement Reporter: Bertrand Delacretaz Priority: Minor Attachments: logo-grid.jpg, logo-solr-d.jpg, logo-solr-e.jpg, logo-solr-source-files-take2.zip, solr-84-source-files.zip, solr-f.jpg, solr-logo-20061214.jpg, solr-logo-20061218.JPG, solr-logo-20070124.JPG, solr-nick.gif, solr.jpg, solr.s1.jpg, solr.svg, solr_logo_it_is_burning.png, sslogo-solr-flare.jpg, sslogo-solr.jpg, sslogo-solr2-flare.jpg, sslogo-solr2.jpg, sslogo-solr3.jpg Following up on SOLR-76, our trainee Nicolas Barbay (nicolas (put at here) sarraux-dessous.ch) has reworked his logo proposal to be more solar. This can either be the start of a logo contest, or if people like it we could adopt it. The gradients can make it a bit hard to integrate, not sure if this is really a problem. WDYT? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
