留言板
Index Checker admin tool - new version
Jorge Díaz,修改在6 年前。
Index Checker admin tool - new version
Liferay Master 帖子: 753 加入日期: 14-1-9 最近的帖子
Hi all,
I have published a new version of Index Checker for both Liferay 6.2 and 7.0/DXP
You can download Index Checker from marketplace:
How it works?
It queries data from both database and index, and matches it, displaying:
- missing objects
- outdated ones
- orphan data in index.
(only primary keys are displayed)
In order to match the data, this portlet compares primary keys, modified dates, status and version attributes of both database and index.
In case of any error, please report your issues in https://github.com/jorgediaz-lr/index-checker/issues, post a comment in this forum or reach me in Twitter @JorgeDiazLr
Regards,
Jorge Díaz
I have published a new version of Index Checker for both Liferay 6.2 and 7.0/DXP
You can download Index Checker from marketplace:
- Marketplace link: https://web.liferay.com/marketplace/-/mp/application/70121999
- Source code: https://github.com/jorgediaz-lr/index-checker
- Issues: https://github.com/jorgediaz-lr/index-checker/issues
How it works?
It queries data from both database and index, and matches it, displaying:
- missing objects
- outdated ones
- orphan data in index.
(only primary keys are displayed)
In order to match the data, this portlet compares primary keys, modified dates, status and version attributes of both database and index.
In case of any error, please report your issues in https://github.com/jorgediaz-lr/index-checker/issues, post a comment in this forum or reach me in Twitter @JorgeDiazLr
Regards,
Jorge Díaz
Denis Signoretto,修改在6 年前。
RE: Index Checker admin tool - new version
Expert 帖子: 375 加入日期: 09-4-21 最近的帖子
Hi Jorge,
thanks fou your update.
I'll check it as soon I can.
Thanks,
Denis.
thanks fou your update.
I'll check it as soon I can.
Thanks,
Denis.
Gopal Satapathy,修改在5 年前。
RE: Index Checker admin tool - new version
Junior Member 帖子: 74 加入日期: 15-7-28 最近的帖子
Hello Jorge,
Can the index checker in any way help me in finding out descripencies in db entry and document library files? I am currently doing migration from 6.2 to DXP 7.1 and the upgrade tool is giving following exception. So is any way index checker or any other tool can help me finding the descripencies ?
2019-02-25 20:14:29.866 ERROR [main][JournalArticleImageUpgradeUtil:88] Unable to get file entry from URL /documents/24059/30825/OnboardingChecklist_Terrein+functies_Manager_aanwerving+na+interim_FR.docx/a925fde7-13a6-4eac-a95c-c8d231160e57
com.liferay.document.library.kernel.exception.NoSuchFileEntryException: No DLFileEntry exists with the key {uuid=a925fde7-13a6-4eac-a95c-c8d231160e57, groupId=24059}
Thanks,
Gopal
Can the index checker in any way help me in finding out descripencies in db entry and document library files? I am currently doing migration from 6.2 to DXP 7.1 and the upgrade tool is giving following exception. So is any way index checker or any other tool can help me finding the descripencies ?
2019-02-25 20:14:29.866 ERROR [main][JournalArticleImageUpgradeUtil:88] Unable to get file entry from URL /documents/24059/30825/OnboardingChecklist_Terrein+functies_Manager_aanwerving+na+interim_FR.docx/a925fde7-13a6-4eac-a95c-c8d231160e57
com.liferay.document.library.kernel.exception.NoSuchFileEntryException: No DLFileEntry exists with the key {uuid=a925fde7-13a6-4eac-a95c-c8d231160e57, groupId=24059}
Thanks,
Gopal
Alberto Chaparro,修改在5 年前。
RE: Index Checker admin tool - new version
Liferay Master 帖子: 549 加入日期: 11-4-25 最近的帖子
Hi Gopal,
In your case the errors are not related to the index. It seems that you have journal artiles with a field pointing a non existing image. The upgrade brings to lights this but you already had this in your original version unless you have too many error like these, if that is the case maybe there is a problem with the DL file system in your new environment. Could you verify it?
Thanks.
In your case the errors are not related to the index. It seems that you have journal artiles with a field pointing a non existing image. The upgrade brings to lights this but you already had this in your original version unless you have too many error like these, if that is the case maybe there is a problem with the DL file system in your new environment. Could you verify it?
Thanks.
Gopal Satapathy,修改在5 年前。
RE: Index Checker admin tool - new version
Junior Member 帖子: 74 加入日期: 15-7-28 最近的帖子
Hello Alberto,
Thanks for your reply. May be i am posting my issue in an incorrect thread. So have created the following thread specific to my issue. Would be great if you can have a look at below thread and help me out.
https://community.liferay.com/forums/-/message_boards/message/113005560
Thanks
Thanks for your reply. May be i am posting my issue in an incorrect thread. So have created the following thread specific to my issue. Would be great if you can have a look at below thread and help me out.
https://community.liferay.com/forums/-/message_boards/message/113005560
Alberto Chaparro
Hi Gopal,
In your case the errors are not related to the index. It seems that you have journal artiles with a field pointing a non existing image. The upgrade brings to lights this but you already had this in your original version unless you have too many error like these, if that is the case maybe there is a problem with the DL file system in your new environment. Could you verify it?
Thanks.
Thanks
Jorge Díaz,修改在5 年前。
RE: Index Checker admin tool - new version
Liferay Master 帖子: 753 加入日期: 14-1-9 最近的帖子
Hi Gopal,
About your comment
Your error seems to be a inconsitence inside your database or a upgrade bug.
Regards,
Jorge Díaz
About your comment
Gopal SatapathyIndex checker only checks inconsistencies between database and search index (elasticsearch/solr)
Can the index checker in any way help me in finding out descripencies in db entry and document library files? I am currently doing migration from 6.2 to DXP 7.1 and the upgrade tool is giving following exception. So is any way index checker or any other tool can help me finding the descripencies ?
Your error seems to be a inconsitence inside your database or a upgrade bug.
Regards,
Jorge Díaz