Florian Semm

You can remove the new id filter query and add the document-limitation as custom-query: ``` php $query->setCustomQuery('id:product_*'); $query->removeFilterQuery('id'); ```

does `omitHeader=true wt=json json.nl=flat q=*:* start=0 rows=12 fl= sort=random_3225 ASC fq=sta:1` works for you?

@muganda ping

Yes it is. You have to consider two things: 1. the document must be placed in a valid entity-mapping directory 2. you must set the hydration-mode to index Example document:...

Your entity/model would look like this ```php /** * @Solr\Document() */ class TestDocument { /** * @Solr\Id() */ protected $id; /** * @Solr\Field() */ protected $name; } ``` You can...

Yes thats true. I have to revert my answer. It is only possible with hacks to query your index. But can can still use the solarium API to get results.

No. The problem is not your field-mapping, is how the bundle filters documents for a given entity/model query.

It think it is not necessary to fork this bundle. You have to overwrite the behavior in https://github.com/floriansemm/SolrBundle/blob/1.6.x/Query/SolrQuery.php#L174. This means you need a new `Query` class and `QueryBuilder::getQuery()` must return...

I will test your pull-request in the end of the week

I have tested your feature with an `Post` entity that has a `tags` property. ``` /** * @Solr\Fields(getter="getTags", fields={ * @Solr\Field(type="integers", getter="getId", fieldAlias="id"), * @Solr\Field(type="strings", getter="getName", fieldAlias="name") * }) *...