-
Notifications
You must be signed in to change notification settings - Fork 467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SiteSearch - items not removed from sitesearch index after unpublish/archive - 5.x #17976
Comments
|
For this ticket we want to apply some improvements: UI improvements:
Cases to handleIncremental
Non-Incremental
|
We found a couple of cases that need to be handle:
09:25:00.532 ERROR job.SiteSearchJobProxy - Elasticsearch exception [type=resource_already_exists_exception, reason=index [cluster_c6148f1ad9.sitesearch_20200312092500/h-yFSeJKTKyoO1XEpOpf1Q] already exists]
org.elasticsearch.ElasticsearchStatusException: Elasticsearch exception [type=resource_already_exists_exception, reason=index [cluster_c6148f1ad9.sitesearch_20200312092500/h-yFSeJKTKyoO1XEpOpf1Q] already exists]
at org.elasticsearch.rest.BytesRestResponse.errorFromXContent(BytesRestResponse.java:177) ~[elasticsearch-7.3.2.jar:7.3.2]
at org.elasticsearch.client.RestHighLevelClient.parseEntity(RestHighLevelClient.java:1727) ~[elasticsearch-rest-high-level-client-7.3.2.jar:7.3.2]
at org.elasticsearch.client.RestHighLevelClient.parseResponseException(RestHighLevelClient.java:1704) ~[elasticsearch-rest-high-level-client-7.3.2.jar:7.3.2]
at org.elasticsearch.client.RestHighLevelClient.internalPerformRequest(RestHighLevelClient.java:1467) ~[elasticsearch-rest-high-level-client-7.3.2.jar:7.3.2]
at org.elasticsearch.client.RestHighLevelClient.performRequest(RestHighLevelClient.java:1439) ~[elasticsearch-rest-high-level-client-7.3.2.jar:7.3.2]
at org.elasticsearch.client.RestHighLevelClient.performRequestAndParseEntity(RestHighLevelClient.java:1406) ~[elasticsearch-rest-high-level-client-7.3.2.jar:7.3.2]
at org.elasticsearch.client.IndicesClient.create(IndicesClient.java:127) ~[elasticsearch-rest-high-level-client-7.3.2.jar:7.3.2]
at com.dotcms.content.elasticsearch.business.ESIndexAPI.createIndex(ESIndexAPI.java:628) ~[classes/:?]
at com.dotcms.enterprise.publishing.sitesearch.ESSiteSearchAPI.createSiteSearchIndex(ESSiteSearchAPI.java:333) ~[classes/:?]
at com.dotcms.publishing.job.SiteSearchJobImpl.run(SiteSearchJobImpl.java:204) ~[classes/:?]
at com.dotcms.publishing.job.SiteSearchJobProxy.run_aroundBody0(SiteSearchJobProxy.java:31) ~[classes/:?]
at com.dotcms.publishing.job.SiteSearchJobProxy$AjcClosure1.run(SiteSearchJobProxy.java:1) ~[classes/:?]
at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149) ~[aspectjrt-1.8.10.jar:?]
at com.dotcms.aspects.aspectj.AspectJDelegateMethodInvocation.proceed(AspectJDelegateMethodInvocation.java:42) ~[classes/:?]
at com.dotcms.aspects.interceptors.CloseDBIfOpenedMethodInterceptor.invoke(CloseDBIfOpenedMethodInterceptor.java:29) ~[classes/:?]
at com.dotcms.aspects.aspectj.CloseDBIfOpenedAspect.invoke(CloseDBIfOpenedAspect.java:41) ~[classes/:?]
at com.dotcms.publishing.job.SiteSearchJobProxy.run(SiteSearchJobProxy.java:17) ~[classes/:?]
at com.dotmarketing.quartz.DotJob.execute(DotJob.java:42) ~[classes/:?]
at org.quartz.core.JobRunShell.run(JobRunShell.java:223) ~[dot.quartz-all-1.8.6_2.jar:?]
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549) ~[dot.quartz-all-1.8.6_2.jar:?]
Suppressed: org.elasticsearch.client.ResponseException: method [PUT], host [https://127.0.0.1:19200], URI [/cluster_c6148f1ad9.sitesearch_20200312092500?master_timeout=30s&timeout=15000ms], status line [HTTP/1.1 400 Bad Request]
The way to reproduce the specific case in the images is to create a
|
PR: #18170 |
Content not found
NOTE: Having a version of the page in spanish and english the search looks right, when the page is just in english I see this behavior. JSP Error in
|
…to the index name to avoid duplicity in concurrent environments
Additional PR to support larger index names: #18269 |
…to the index name to avoid duplicity in concurrent environments (#18269) Co-authored-by: Nollymar Longa <>
Fixed, tested after the last changes and this is ok for now, more work reported in new cards |
Describe the bug
Unpublishing and/or archiving items does not remove them from a SiteSearch index.
Steps to reproduce the behavior:
Recreated on demo.dotcms.com
Content is still found
Expected behavior
Content should be removed from SiteSearch index.
Actual behavior
Content is still found
Screenshots
Create new content
Create new SiteSearch index (newIndex)
Search SiteSearch Index
Unpublish/Archive Content
Run SiteSearch job on your new index
Search SiteSearch index... Content is still there
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: