Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change 
notification.

The following page has been changed by HossMan:
http://wiki.apache.org/solr/TaskList

The comment on the change is:
noting some things i know are done, and adding new brainstorming page

------------------------------------------------------------------------------
  
  This section should be used for ideas that are more involved and may require 
major changes to the Solr codebase, and definitely should involve a lot of 
discussion among developers about the appropriate way to tackle them...
  
+   * Robust and configurable field aliasing and globbing support: 
FieldAliasesAndGlobsInParams
    * Alternate replication strategy that can work on Windows?
     * NTFS w/ WinXP or later does support hard links for files (and cygwin 
"ln" works for files).  The current replication scripts could be ported to 
cygwin.
    * Support for IndexPartitioning within a single solr webapp instance
    * A more powerful query language allowing one to express complicated logic 
without resorting to a custom Java query handler plugin.
    * Make use of [http://jakarta.apache.org/hivemind/ HiveMind] or Spring for 
configuration & dependency injection
-   * utilize Lucene's new field selector / lazy field loading mechanism to 
speed up requests that select only a few stored fields out of many.  Beware 
interaction with the DocCache... it may need to be modified or bypassed. (see 
also [http://issues.apache.org/jira/browse/SOLR-52 SOLR-52])
+   * [DONE] utilize Lucene's new field selector / lazy field loading mechanism 
to speed up requests that select only a few stored fields out of many.  Beware 
interaction with the DocCache... it may need to be modified or bypassed. (see 
also [http://issues.apache.org/jira/browse/SOLR-52 SOLR-52])
-   * Implement flexible autoCommit/autoOptimize criteria (see  
[http://issues.apache.org/jira/browse/SOLR-65 SOLR-65] for some discussion)
+   * [DONE] Implement flexible autoCommit/autoOptimize criteria (see  
[http://issues.apache.org/jira/browse/SOLR-65 SOLR-65] for some discussion)
    * Implement some ideas for ComplexFacetingBrainstorming
    * Implement some ideas to MakeSolrMoreSelfService
    * [DONE via defaults and DateMath] support for an an optional "timestamp" 
style field in schemas which always want every doc to include the datetime the 
document was added to the index.  This might be a special case (like the 
uniqueKey field) or it could involve more general "default" support for fields 
and fieldtypes (ie: `<field>` and `<fieldtype>` declarations could include a 
`default="..."` attribute that gets put into any document that doesn't already 
have a value for that field, with the underlying !FieldType parsing the text 
each time it's used, so that the !DateField class can convert `default="now"` 
to the current time.
@@ -74, +75 @@

    * investigate this 
"[http://mail-archives.apache.org/mod_mbox/lucene-java-user/200603.mbox/[EMAIL 
PROTECTED] SynonymQuery]" and how !SynonymFilter might be modified to set token 
types to trigger it's use automatically in !SolrQueryParser
    * FederatedSearch
    * A "user query" parameter for standard request handler, much like what 
dismax handler has, for unstructured queries entered from a search box
+     * [DONEish?] ... the QParser abstraction and the components framework 
have basically make dismax and standard the same now
    * refactor and separate update XML parsing from update handling... possibly 
implement support for JSON updates.
+     * [DONEish?] the refactoring is done, but still no JSON update support 
-   * refactor all of the JSP pages into servlets so a JDK/JSP compiler isn't 
needed (the current JSPs are very sparse on presentation, and use no custom 
tags, so there is almost no advantage to them being JSPs)
+   * [IN PROGRESS] refactor all of the JSP pages into request handler so a 
JDK/JSP compiler isn't needed (the current JSPs are very sparse on 
presentation, and use no custom tags, so there is almost no advantage to them 
being JSPs)
    * Better handling of arbitrary XML charsets: see 
[http://issues.apache.org/jira/browse/SOLR-96 SOLR-96]
    * Better support for tagging: UserTagDesign
  

Reply via email to