Thanks, Erick. I have tried it four times. It keeps failing. The problem reoccurred today.
Thanks. -----Original Message----- From: Erick Erickson [mailto:erickerick...@gmail.com] Sent: Monday, July 29, 2013 2:44 AM To: solr-user@lucene.apache.org Subject: Re: new field type - enum field You should be able to attach a patch, wonder if there was some temporary glitch in the JIRA. Is this persisting. Let us know if this continues... Erick On Sun, Jul 28, 2013 at 12:11 PM, Elran Dvir <elr...@checkpoint.com> wrote: > Hi, > > I have created an issue: > https://issues.apache.org/jira/browse/SOLR-5084 > I tried to attach my patch, but it failed: " Cannot attach file > Solr-5084.patch: Unable to communicate with JIRA." > What am I doing wrong? > > Thanks. > > -----Original Message----- > From: Erick Erickson [mailto:erickerick...@gmail.com] > Sent: Thursday, July 25, 2013 3:25 PM > To: solr-user@lucene.apache.org > Subject: Re: new field type - enum field > > Start here: http://wiki.apache.org/solr/HowToContribute > > Then, when your patch is ready submit a JIRA and attach your patch. Then > nudge (gently) if none of the committers picks it up and applies it.... > > NOTE: It is _not_ necessary that the first version of your patch is > completely polished. I often put up partial/incomplete patches (comments with > //nocommit are explicitly caught by the "ant precommit" target for instance) > to see if anyone has any comments before polishing..... > > Best > Erick > > On Thu, Jul 25, 2013 at 5:04 AM, Elran Dvir <elr...@checkpoint.com> wrote: >> Hi, >> >> I have implemented like Chris described it: >> The field is indexed as numeric, but displayed as string, according to >> configuration. >> It applies to facet, pivot, group and query. >> >> How do we proceed? How do I contribute it? >> >> Thanks. >> >> -----Original Message----- >> From: Chris Hostetter [mailto:hossman_luc...@fucit.org] >> Sent: Thursday, July 25, 2013 4:40 AM >> To: solr-user@lucene.apache.org >> Subject: Re: new field type - enum field >> >> >> : Doable at Lucene level by any chance? >> >> Given how well the Trie fields compress (ByteField and ShortField have been >> deprecated in favor of TrieIntField for this reason) it probably just makes >> sense to treat it as a numeric at the Lucene level. >> >> : > If there's positive feedback, I'll open an issue with a patch for the >> functionality. >> >> I've typically dealt with this sort of thing at the client layer >> using a simple numeric field in Solr, or used an UpdateProcessor to >> convert the >> String->numeric mapping when indexing & used clinet logic of a >> DocTransformer to handle the stored value at query time -- but having a >> built in FieldType that handles that for you automatically (and helps ensure >> the indexed values conform to the enum) would certainly be cool if you'd >> like to contribute it. >> >> >> -Hoss >> >> Email secured by Check Point > > Email secured by Check Point Email secured by Check Point
