Alex Garel

@herrnici, given your usecase, why don't you simply override `get_queryset` in you `Document` class ?

@prasad4491 if you do a populate, is there data ?  See https://django-elasticsearch-dsl.readthedocs.io/en/latest/quickstart.html#populate You may have not setup correctly. Also be attentive to any warning message from django.

You didn't understand the purpose of `to_queryset`. The docstring says : This method return a django queryset from an elasticsearch result. So `RoomDocument.search().to_queryset()` would simply (in most configuration) be equivalent...

@khaldon, this place is for bug report. Please next, time use stackoverflow for support. Maybe you wan't something like : ```python user = get_object_or_404(CustomUser,username=request.user.username) results = RoomDocument.search().filter("terms", _id=user.teacher_rooms.all()) ``` But...

Please, post that kind of question on stackoverflow with the django-elasticsearch-dsl tag. Not here.

ElasticSearch recommends you to have one object type per index. So you can tweak the way you've done, but this shall not be the default. The default is to have...

Yes the good way of handling this with celery is to pass the id of the database object to save. But there is another pitfall: if your database is running...

You can also provide your own `prepare__price(self, obj)` method.

Hi @thclark it seems like a good idea. A PR, with docs and unit test will be accepted I imagine :-) (though I'm not a maintainer)

Hello @shyam81295, This is a good idea to support it. We should also consider supporting the original Lucene format (where ["now" is "NOW"](https://lucene.apache.org/solr/4_4_0/solr-core/org/apache/solr/schema/DateField.html)). Right now this won't be on our...