search for: cachet

...#39;s listed as a "selling point" of SOLR versus other > full text search engines: > > 4) The ability to do searches against any attachments that are able to be > post-processed and hyper-indexed by SOLR+Tika? > > ------------- > > SOLR seems to have "brand cachet", so presumably it actually works (for somebody). > > Dovecot has not a little "brand cachet", and for me, I have innate faith and > trust in Timo and his software. I am no stranger to the "costs" of "free" > software, in that you sacrifice your own b...

...ot; of SOLR versus other > > full text search engines: > > > > 4) The ability to do searches against any attachments that are able to be > > post-processed and hyper-indexed by SOLR+Tika? > > > > ------------- > > > > SOLR seems to have "brand cachet", so presumably it actually works (for somebody). > > > > Dovecot has not a little "brand cachet", and for me, I have innate faith and > > trust in Timo and his software. I am no stranger to the "costs" of "free" > > software, in that you...

...; > > 4) The ability to do searches against any attachments that are > > > > able to be > > > > post-processed and hyper-indexed by SOLR+Tika? > > > > > > > > ------------- > > > > > > > > SOLR seems to have "brand cachet", so presumably it actually > > > > works (for somebody). > > > > > > > > Dovecot has not a little "brand cachet", and for me, I have > > > > innate faith and > > > > trust in Timo and his software. I am no stranger to the...

The real main differecne seems coming from "diffconfig.xml" When I put yours, Solr delete (!) schema.xml and create a "manage-schema" and starts complaining about useless types (tdates, booleans, etc..) that are not needed for Mail fileds When I put mine (from standard distribution of Arch), it keeps things as they are (yeah !), does not complains about those useless types

Hi I read that bundles are to be deprecated in 2.10. The BACCO bundle contains three packages (emulator, calibrator, approximator) which I am happy to unbundle. But the 'BACCO' moniker has some considerable cachet for me in terms of recognizability (eg with grant-giving bodies), as it has become an umbrella term for a whole bunch of related statistical functionality of which the three packages are examples. I make heavy use of the word "BACCO" in my publications. If bundles were to be supported i...

...of the above, despite the fact that it's listed as a "selling point" of SOLR versus other full text search engines: 4) The ability to do searches against any attachments that are able to be post-processed and hyper-indexed by SOLR+Tika? ------------- SOLR seems to have "brand cachet", so presumably it actually works (for somebody). Dovecot has not a little "brand cachet", and for me, I have innate faith and trust in Timo and his software. I am no stranger to the "costs" of "free" software, in that you sacrifice your own blood, sweat, and tea...

...#39;s listed as a "selling point" of SOLR versus other > full text search engines: > > 4) The ability to do searches against any attachments that are able to be > post-processed and hyper-indexed by SOLR+Tika? > > ------------- > > SOLR seems to have "brand cachet", so presumably it actually works (for somebody). > > Dovecot has not a little "brand cachet", and for me, I have innate faith and > trust in Timo and his software. I am no stranger to the "costs" of "free" > software, in that you sacrifice your own b...

...#39;s listed as a "selling point" of SOLR versus other > full text search engines: > > 4) The ability to do searches against any attachments that are able to be > post-processed and hyper-indexed by SOLR+Tika? > > ------------- > > SOLR seems to have "brand cachet", so presumably it actually works (for somebody). > > Dovecot has not a little "brand cachet", and for me, I have innate faith and > trust in Timo and his software. I am no stranger to the "costs" of "free" > software, in that you sacrifice your own b...

...#39;s listed as a "selling point" of SOLR versus other > full text search engines: > > 4) The ability to do searches against any attachments that are able to be > post-processed and hyper-indexed by SOLR+Tika? > > ------------- > > SOLR seems to have "brand cachet", so presumably it actually works (for somebody). > > Dovecot has not a little "brand cachet", and for me, I have innate faith and > trust in Timo and his software. I am no stranger to the "costs" of "free" > software, in that you sacrifice your own b...

Hi, Kunaal and I have completed a prototype of the first part of our GSoC project (implement a new doc toolchain). Our goal is to implement a doc toolchain for short how-to docs and lower the barrier for new comers to contribute. This is the workflow of the prototype: 1. Contributor creates a new pull request on GitHub 2. A corresponding issue is automatically created on Pagure 3. Staff and

Hello, I'm learning about robust M-estimators right now and had settled on the "Huber Proposal 2" as implemented in MASS, but further reading made clear, that at least 2 further weighting functions (Hampel, Tukey bisquare) exist. In a post from B.D. Ripley going back to 1999 I found the following quote: >> 2) Would huber() give me results that are similar (i.e., close

...ing to be dense, but I want to make sure I understand the > goals here: > > This is the workflow of the prototype: > 1. Contributor creates a new pull request on GitHub > > > A fairly well understand platform with lots of potential users - cool. > Github also has some social cachet. > That's the aim. Exploit this social cachet. > > 2. A corresponding issue is automatically created on Pagure > 3. Staff and contributor discuss on Pagure > > > This part is a bit odd to me, today. I believe your goal is to make sure > the discussion happens in a Cen...

...o contribute. I am not trying to be dense, but I want to make sure I understand the goals here: > This is the workflow of the prototype: > 1. Contributor creates a new pull request on GitHub A fairly well understand platform with lots of potential users - cool. Github also has some social cachet. > 2. A corresponding issue is automatically created on Pagure > 3. Staff and contributor discuss on Pagure This part is a bit odd to me, today. I believe your goal is to make sure the discussion happens in a CentOS controlled space in case github ever becomes an issue. However, it seems...