Fwd: Google Summer of Code
FYI - as I said before, I'm unable to mentor a project this year, unfortunately. -- Forwarded message -- From: Ross Gardler [EMAIL PROTECTED] Date: Mar 14, 2007 2:53 PM Subject: Google Summer of Code To: [EMAIL PROTECTED], [EMAIL PROTECTED] Google are due to announce the accepted organisations in the Google Summer of Code today. Unfortunately, I've been really busy with other things recently and have not managed to organise the ASF application as well as I might. However, I did manage to notify the [EMAIL PROTECTED] list of the process and I did get an application in on time. So, now to the next stage. This message is mailed to members@ as well as [EMAIL PROTECTED] Please feel free to distribute to your projects, I chose not to send to community@ or committers@ because I'm aware different projects like to manage GSoC applications in different ways. It's up to the members to take this forward in individual projects. Student applications will open today and will close on March 24th. If your projects want to accept applications from GSoC students then you need to ensure you have details listed on http://wiki.apache.org/general/SummerOfCode2007 If you want more info on what being a mentor means then a good place to start is http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors Interested parties should also subscribe to [EMAIL PROTECTED] where all internal communication about GSoC occurs (like how we select which projects to accept). Ross
[jira] Assigned: (SOLR-188) bin scripts do not support non-default webapp names
[
https://issues.apache.org/jira/browse/SOLR-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Au reassigned SOLR-188:
Assignee: Bill Au
bin scripts do not support non-default webapp names
---
Key: SOLR-188
URL: https://issues.apache.org/jira/browse/SOLR-188
Project: Solr
Issue Type: Bug
Components: update
Affects Versions: 1.1.0, 1.2
Environment: Unix/Linux operating systems
Reporter: Jeff Rodenburg
Assigned To: Bill Au
Fix For: 1.1.0, 1.2
Attachments: scripts_url.patch
If the solr web application has been configured in a non-default location,
i.e. http://localhost:8080/solrapp2/, the operation scripts under
http://localhost:8080/solrapp2/bin/ will fail. The current logic assumes the
location to be {hostname}:{port}/solr.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-188) bin scripts do not support non-default webapp names
[
https://issues.apache.org/jira/browse/SOLR-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481157
]
Bill Au commented on SOLR-188:
--
The patch looks good. I am going to commit it and update the related
documentation in the Solr Wiki.
bin scripts do not support non-default webapp names
---
Key: SOLR-188
URL: https://issues.apache.org/jira/browse/SOLR-188
Project: Solr
Issue Type: Bug
Components: update
Affects Versions: 1.1.0, 1.2
Environment: Unix/Linux operating systems
Reporter: Jeff Rodenburg
Assigned To: Bill Au
Fix For: 1.1.0, 1.2
Attachments: scripts_url.patch
If the solr web application has been configured in a non-default location,
i.e. http://localhost:8080/solrapp2/, the operation scripts under
http://localhost:8080/solrapp2/bin/ will fail. The current logic assumes the
location to be {hostname}:{port}/solr.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SOLR-188) bin scripts do not support non-default webapp names
[
https://issues.apache.org/jira/browse/SOLR-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Au resolved SOLR-188.
--
Resolution: Fixed
Thanks Jeff for the patch. It has been applied. I have also updated the Solr
Wiki:
http://wiki.apache.org/solr/SolrOperationsTools
bin scripts do not support non-default webapp names
---
Key: SOLR-188
URL: https://issues.apache.org/jira/browse/SOLR-188
Project: Solr
Issue Type: Bug
Components: update
Affects Versions: 1.1.0, 1.2
Environment: Unix/Linux operating systems
Reporter: Jeff Rodenburg
Assigned To: Bill Au
Fix For: 1.1.0, 1.2
Attachments: scripts_url.patch
If the solr web application has been configured in a non-default location,
i.e. http://localhost:8080/solrapp2/, the operation scripts under
http://localhost:8080/solrapp2/bin/ will fail. The current logic assumes the
location to be {hostname}:{port}/solr.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-124) use NewIndexModifier, LUCENE-565
[ https://issues.apache.org/jira/browse/SOLR-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481238 ] Hoss Man commented on SOLR-124: --- no patch exists yet ... this issue was opened to track that it *should* be done at some point. i believe it will be a somewhat significant change, but i'm not much of an expert on the update internals. use NewIndexModifier, LUCENE-565 Key: SOLR-124 URL: https://issues.apache.org/jira/browse/SOLR-124 Project: Solr Issue Type: Improvement Components: update Reporter: Yonik Seeley LUCENE-565 adds extension points to the IndexWriter, and adds delete-by-term functionality. We should probably take advantage of this (when available) in our UpdateHandler (a new one, or modify DU2?) and perhaps implement a more efficient deleteByQuery. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-124) use NewIndexModifier, LUCENE-565
[ https://issues.apache.org/jira/browse/SOLR-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481264 ] Mike Klaas commented on SOLR-124: - DUH may be simpler, but DUH2 has also been carefully modified to safely support multithreaded indexing and autocommitting. Does anyone have a feeling on whether LUCENE-565 will improve performance? Or is it likely to be mostly a code cleansliness improvement? use NewIndexModifier, LUCENE-565 Key: SOLR-124 URL: https://issues.apache.org/jira/browse/SOLR-124 Project: Solr Issue Type: Improvement Components: update Reporter: Yonik Seeley LUCENE-565 adds extension points to the IndexWriter, and adds delete-by-term functionality. We should probably take advantage of this (when available) in our UpdateHandler (a new one, or modify DU2?) and perhaps implement a more efficient deleteByQuery. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: New Jira Hudson plugin
Jira issue numbers should now be hyper-linked to Jira. Also, in the Hadoop-Nightly build I'm experimenting with a feature of the plugin that will update the Jira with a link back to the Hudson build in which it was integrated. For example https:// issues.apache.org/jira/browse/HADOOP-1115 now has such a link. If other projects (Lucene, Nutch, Solr) want this feature turned on then please let me know. More on the new plugin here: http://weblogs.java.net/blog/kohsuke/archive/2007/03/ hudsonjira_inte.html I'm not sure what is the magic behind this plugin - Nutch still follows a simplified JIRA workflow (although in my opinion we should switch to the same workflow as Hadoop uses), and this simplified workflow doesn't contain patch available state. Hi Andrzej, I suspect you may be confusing this with the automatic build we do for Hadoop when someone submits a patch to Jira and marks it Patch Available. This new plugin has nothing to do with Jira states or our custom Hadoop patch build process. Husdon has always noticed the changes that were integrated into each successive build. For instance, look at: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/24/ This Jira plugin simply does 2 additional things. 1) Whenever is sees what is suspects is a Jira issue number in the build change log, it will hyper-link to the issue. 2) It can also add a comment to the Jira's that were integrated into each build, but this functionality has to be enabled for each build project. An example of the comment it adds can be seen in this recently integrated Hadoop defect: http://issues.apache.org/jira/browse/HADOOP-1115#action_12480723 Let me know if you want item #2 functionality enabled for Nutch. [ditto for Lucene and Solr, who I have cc'd] Cheers, Nige
