Search Engine using Django-Python

240 views
Skip to first unread message

Manoj Bawane

unread,
Jul 6, 2015, 4:01:36 PM7/6/15
to django...@googlegroups.com
Hi All,

I am planning to create a search engine for my city. Can you please suggest me Which technology I should prefer? I am new with Django, before that I have work with some web application using Java Spring. But now, I recently working in one project where I found Django is also nice framework to develop search engine sites. So Please any one suggest me,
  1. How should I proceed to do this project using Django,
  2. What other technology associated with Django which helps to make searching faster.
  3. Which Open Source database will better
  4. Where I can deploy my search engine, (will it need dedicated or shared host server).
Please suggest your valuable opinion.


Thanks to everyone.

Daniel França

unread,
Jul 6, 2015, 4:06:43 PM7/6/15
to django...@googlegroups.com
Hi Manoj, have you tried Haystack? http://haystacksearch.org/
It's a simple API to make a search engine using Django, and you can attach any of the available backends (Solr, Elasticsearch, Whoosh or Xapian).

Best,
Daniel


--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/564fdc15-391d-4829-bdb2-96d189d73499%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Manoj Bawane

unread,
Jul 21, 2015, 7:17:43 PM7/21/15
to django...@googlegroups.com
Hi Daniel,

Yes, I read about Haystack and I am implementing it with Solr and Database I am using MySQL. While integrating it I am getting error for ManyToMany Model field.
I am getting this error and I am not understand what is going wrong or what to do:

Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/haystack/management/commands/update_index.py", line 210, in handle_label
    self.update_backend(label, using)
  File "/usr/local/lib/python2.7/dist-packages/haystack/management/commands/update_index.py", line 256, in update_backend
    do_update(backend, index, qs, start, end, total, self.verbosity)
  File "/usr/local/lib/python2.7/dist-packages/haystack/management/commands/update_index.py", line 78, in do_update
    backend.update(index, current_qs)
  File "/usr/local/lib/python2.7/dist-packages/haystack/backends/solr_backend.py", line 49, in update
    docs.append(index.full_prepare(obj))
  File "/usr/local/lib/python2.7/dist-packages/haystack/indexes.py", line 196, in full_prepare
    self.prepared_data = self.prepare(obj)
  File "/home/manoj/final-s4s-project/search4school/search4schoolapp/search_indexes.py", line 30, in prepare
    data = super(CollegeIndex, self).prepare(obj)
  File "/usr/local/lib/python2.7/dist-packages/haystack/indexes.py", line 187, in prepare
    self.prepared_data[field.index_fieldname] = field.prepare(obj)
  File "/usr/local/lib/python2.7/dist-packages/haystack/fields.py", line 152, in prepare
    return self.convert(super(CharField, self).prepare(obj))
  File "/usr/local/lib/python2.7/dist-packages/haystack/fields.py", line 100, in prepare
    return current_object()
  File "/usr/local/lib/python2.7/dist-packages/django/db/models/fields/related.py", line 843, in __call__
    manager = getattr(self.model, kwargs.pop('manager'))
KeyError: u'manager'

Ajeeb K P

unread,
Jul 24, 2015, 9:23:26 AM7/24/15
to Django users, bawane....@gmail.com
I think you have to head this way.

https://docs.djangoproject.com/en/1.8/topics/db/managers/

According to this docs,

A Manager is the interface through which database query operations are provided to Django models. At least one Manager exists for every model in a Django application.

So, IMHO, you should check about solr and saving. I am not expert at things related to Solr, elastic search etc. But, i doubt it would be wrong with Solr.

jirka.v...@gmail.com

unread,
Jul 24, 2015, 10:35:20 AM7/24/15
to django...@googlegroups.com
Hi Manoj,

I'm very happy with django-watson + PostgreSQL combination. It's a relatively low-tech option, but works very well for me.

HTH

Jirka

From: Manoj Bawane <bawane....@gmail.com>
Date: Mon, 6 Jul 2015 08:25:57 -0700 (PDT)
Subject: Search Engine using Django-Python
Reply all
Reply to author
Forward
0 new messages