Archive for the ‘search & find’ Category

Using different URL for Apache Solr post.jar

If you want to use the post.jar of Apache Solr to post content to Solr, you can change the used Solr Server URL via

java -Durl=http://MYSERVER-URL:8080/solr/update -jar post.jar document.xml

where MYSERVER-URL should be your Solr Server URL and 8080 the correct port.

Thinking Sphinx attribute filter and negative values

Just wondered why I got no results after executing a search via Sphinx and Thinking Sphinx. The problem was, that I used a negative value in a filter attribute and that Sphinx only supports unsigned integers:

Attributes are named. Attribute names are case insensitive. Attributes are not full-text indexed; they are stored in the index as is. Currently supported attribute types are:

  • unsigned integers (1-bit to 32-bit wide);
  • UNIX timestamps;
  • floating point values (32-bit, IEEE 754 single precision);
  • string ordinals (specially computed integers);
  • strings (since 1.10-beta);
  • MVA, multi-value attributes (variable-length lists of 32-bit unsigned integers).
  • Official Google Blog: Our new search index: Caffeine

    Google Logo bg:Картинка:Google.png
    Image via Wikipedia

    Caffeine provides 50 percent fresher results for web searches than our last index, and it's the largest collection of web content we've offered. Whether it's a news story, a blog or a forum post, you can now find links to relevant content much sooner after it is published than was possible ever before.

    via Official Google Blog: Our new search index: Caffeine.

    Apache Lucene and Ruby

    Robert Dempsey has written a nice article about ‘Using Amazon S3, EC2, SQS, Lucene, and Ruby for Web Spidering‘, which is very interesting because it describes how to interact with Apache Lucene using Ruby.

    Reblog this post [with Zemanta]

    next-generation architecture for Google's web search

    For the last several months, a large team of Googlers has been working on a secret project: a next-generation architecture for Google’s web search. It’s the first step in a process that will let us push the envelope on size, indexing speed, accuracy, comprehensiveness and other dimensions. The new infrastructure sits “under the hood” of Google’s search engine, which means that most users won’t notice a difference in search results. But web developers and power searchers might notice a few differences, so we’re opening up a web developer preview to collect feedback.
    (see Google Webmaster Central)

    Reblog this post [with Zemanta]

    Clusty. My new favourite search engine.

    It’s a shame that i didn’t recognize this thing of beauty before. :)

    Clusty

    searchCrystal. search visualization tool

    searchCrystal lets you search and compare multiple engines in one place.
    It is a search visualization tool that enables you to compare, remix and share results from the best web, image, video, blog, tagging, news engines, Flickr images or RSS
    feeds.

    (more…)

    krugle code search engine

    Just found krugle. A nifty search engine which helps you finding source-code by searching through projects which are available in the internet. It also allows you to add comments to the code.

    Krugle helps programmers find existing source code and the information they need to evaluate, deploy and fix code.

    There is a demo-video which shows all the features.

    I found my code at Krugle

    Grokker. Now and then.

    I have tested Grooker — a really nice looking search-engine — some years ago, when it was a desktop-application. Seems that it has become a web-application since then. Its still nice looking and returns good results.grokker webapplication

    Search Wikia

    Thanks to Dave Winer’s posting, i have found out about Search Wikia.

    The basic concept of the search project is that I want to create a completely transparent, open-source, freely licensed search engine, [...]
    (more @ infoworld.com)

    DBpedia II.

    Just found another posting about DBpedia in a blog of one of the developers. It tells you a little bit more about the backgrounds of this great project.

    Taking Wikipedia to the next level

    Just read something about the following project:

    DBpedia.org is a community effort to extract structured information from Wikipedia and to make this information available on the Web. DBpedia allows you to ask sophisticated queries against Wikipedia and to link other datasets on the Web to Wikipedia data.

    Instead of searching the full-text of Wikipedia, it allows you to execute SPARQL-Queries on the data. With “the data” i mean RDF-Data. Because the goal of the DBpedia-project is to create a whole bunch of structured data out of the Wikipedia-texts.

    A little search interface can be found at http://dbpedia.org/search/.

    Next Page »" class="small button">older posts