Martin A. Posted September 27, 2018 Share Posted September 27, 2018 Since Elastic was enabled we've had to overload the updateViewCounts() method in \IPS\Content\Search\Elastic\Index with this, /** * Update view count * * @param string $class Class to update * @param int $id ID of item * @param int $count Count to update * @throws \OutOfRangeException When table to update no longer exists */ final public function updateViewCounts( $class, $id, $count ) { /* This doesn't work at all. */ return; } We're not experiencing any slowness anymore. The only feature we're missing out on is the ability to filter search result by views, which to be honest is not an important feature. Link to comment Share on other sites More sharing options...
yacenty Posted September 27, 2018 Share Posted September 27, 2018 we did the same here is the cpu load chart and zabbix elastic index operations Link to comment Share on other sites More sharing options...
DSystem Posted September 27, 2018 Share Posted September 27, 2018 On 5/4/2018 at 10:02 AM, DSyste said: I believe that the search index should be built in the background. This would avoid delaying the posts, regardless of the Elasticsearch server configuration. In this new version of IPS 4.3.6, the search index is built in the background? Link to comment Share on other sites More sharing options...
Spanner Posted September 28, 2018 Share Posted September 28, 2018 @Matt You using deprecated field in Elastic request. [2018-09-28T01:51:10,685][WARN ][o.e.d.c.ParseField ] Deprecated field [inline] used, expected [source] instead Please change this in next version, because in next elastic version this won't work Link to comment Share on other sites More sharing options...
bearback Posted May 17, 2019 Share Posted May 17, 2019 On 9/28/2018 at 7:14 AM, Spanner said: @Matt You using deprecated field in Elastic request. [2018-09-28T01:51:10,685][WARN ][o.e.d.c.ParseField ] Deprecated field [inline] used, expected [source] instead Please change this in next version, because in next elastic version this won't work Sorry to bump up an old topic, I am using IPB 4.3.6 and elasticsearch installed on my server, checking my ipb-forum-deprecation log in elasticsearch I have loads of these entry's. [2019-05-17T10:06:01,802][WARN ][o.e.d.c.ParseField ] Deprecated field [inline] used, expected [source] instead is there a fix for this issue ? Thank you Link to comment Share on other sites More sharing options...
bfarber Posted May 17, 2019 Share Posted May 17, 2019 3 hours ago, bearback said: Sorry to bump up an old topic, I am using IPB 4.3.6 and elasticsearch installed on my server, checking my ipb-forum-deprecation log in elasticsearch I have loads of these entry's. [2019-05-17T10:06:01,802][WARN ][o.e.d.c.ParseField ] Deprecated field [inline] used, expected [source] instead is there a fix for this issue ? Thank you It's a warning about a deprecated field - it's not an issue and can be safely ignored. (We still support ES 5 which uses that field) Link to comment Share on other sites More sharing options...
bearback Posted May 18, 2019 Share Posted May 18, 2019 23 hours ago, bfarber said: It's a warning about a deprecated field - it's not an issue and can be safely ignored. (We still support ES 5 which uses that field) thank you for your reply Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.