amathur
Forum Replies Created
-
Forum: Reviews
In reply to: [WPSOLR - Elasticsearch and Solr search] Awesome Plugin!Hi,
This project has been developed for an end-client, so I am unsure if I will have approval for the same.
However, I shall speak with the client and come back in case we can do that.Forum: Plugins
In reply to: [WPSOLR - Elasticsearch and Solr search] Not indexing data custom fieldsStill waiting for an answer for this???
Forum: Plugins
In reply to: [WPSOLR - Elasticsearch and Solr search] Unable to resume indexingStill waiting for an answer on this????
Forum: Plugins
In reply to: [WPSOLR - Elasticsearch and Solr search] Not indexing data custom fieldsAlso, above solution never worked. But custom fields did get indexed and now they are not getting indexed.
Please provide a complete answer on how to manage custom fields indexing.
Forum: Plugins
In reply to: [WPSOLR - Elasticsearch and Solr search] Not indexing data custom fieldsThen why does the SOLR Options screen in your plugin show “Custom Fields to be indexed”???
Forum: Plugins
In reply to: [WPSOLR - Elasticsearch and Solr search] Unable to resume indexingSo, if I downgrade the version to 1.7 will it solve my problem and indexing all remaining documents?
Please confirm.Forum: Plugins
In reply to: [WPSOLR - Elasticsearch and Solr search] Not indexing data custom fieldsI am also facing the same issue. In earlier versions, custom fields were getting indexed.
This problem may cause huge problems to me since I have a very huge dataset and some part of it has custom fields indexed, which happened on earlier WPSOLR version and new set which has no custom fields indexed.
Forum: Plugins
In reply to: [WPSOLR - Elasticsearch and Solr search] Unable to resume indexingPlease elaborate how this is to be done with previous version.
Forum: Plugins
In reply to: [WPSOLR - Elasticsearch and Solr search] Unable to resume indexingand how many docs in Solr (/select?q=*%3A*) ?
>> 3903847Forum: Plugins
In reply to: [WPSOLR - Elasticsearch and Solr search] Unable to resume indexinghow many docs the query returns ?
>> The query returns 734433 docshow many docs the query returns if you remove the post_modified condition ?
>> Removing the post_modified condition, the query returns 7262480 docsForum: Plugins
In reply to: [WPSOLR - Elasticsearch and Solr search] Unable to resume indexingNot sure how this can be done.
If WPSOLR is not storing any flag against each post to mark it as indexed/not indexed, I guess there is no way to do this. I believe this is a serious bug.
Also, please note that SOLR will be used in such situations only, where the document size is huge, else there is no need for it in normal WP sites. So you need to have an elegant mechanism to determine posts indexed and not, without relying on just the last indexed date.
Forum: Plugins
In reply to: [WPSOLR - Elasticsearch and Solr search] Unable to resume indexingThe query is correct and showing rightly the post types selected for indexing.
SELECT count(ID) as TOTAL FROM wp_posts WHERE post_modified > %s AND ( post_status=’publish’ AND ( post_type=’company’ OR post_type=’person’ OR post_type=’location’ ) )
Yet the count is incorrect of pending documents.
Forum: Plugins
In reply to: [WPSOLR - Elasticsearch and Solr search] Unable to resume indexingThanks a lot for your help and suggestions.
I followed the steps outlined and here is what I got –
A total of 3903813 documents are currently in your index.
734425 document(s) remain to be indexed.But the pending documents value does not match the remaining posts.
It should be close to 33 Lac and not just around 7 Lac!Please check.
Forum: Plugins
In reply to: [WPSOLR - Elasticsearch and Solr search] Unable to resume indexingSorry, but I am not convinced with your answer.
You should have provided some disclaimer as I am now stuck with this plugin.Forum: Plugins
In reply to: [WPSOLR - Elasticsearch and Solr search] Unable to resume indexingThis is a very sad answer.
How can you change basic idea of how the plugin works?I have 40 Lac posts indexed and cannot delete all this indexed data as it has taken weeks!!!!
This is a very bad way to upgrade any plugin, leave alone upgrade such a critical one. Also, did you specify this change in any of your change logs? I am very disappointed with this answer.
Please suggest some other way as I will loose weeks of work!!!!