liferay - Can't Reindex All Search Indexes [SOLVED] -


I recently removed 120,000 users from my Liferay database using an automated script. the User_ WHERE userId = 1234567 deleted database deleted manually 2 user databases by using - it is to see what can be the user can do with it .

The user was removed, but the user ID is retaining all other table rows holding the ID (1234567). Okay.

So now I am at a point where I want to add all the search index again to get the current list of users, but LR throws an exception:

  Error 08: 07: 41,922 [http-Bio-20110-exec-290] [Lucinindexer: 136] Com. The error has to be encountered while re-flowing on the lififier. Portable.kernel.search.SearchException: com.liferay.portal.NoSuchUserE xception: not com.liferay.portlet.usersadmin.util user com.liferay.portal.kernel.search.baseIndexer.getDocument (BaseIndexer.j ava: 179) .ContactIndexer exists with the $ 1 key on {contactId = 1234568} Kprform action .java: 203) InSingleInterval on com.liferay.portal.kernel.dao.orm.BaseActionableDynamicQuery.performActions (com.liferay.portal.kernel.dao on BaseActionableDynamicQuery.java.309) on .orm.BaseActionableDynamicQuery.performActi  <

so my question is, how it can be more of the same points userId to any user ( I may be wrong about that)

I have this proble Programming can precisely meter so I can reindex?

Liferay EE 6.2 Tomket 7.0.33 SQL Server

I found that manually For the deleted user, contactId is still in the contact _ table. I removed it from the table and now I can now reinstall all users & amp; User group after readerxing.

From LR:

Rules Liferay - database to use # 1, you should never do it and you should never released SQL against it .

Liferay is the only way to modify API data. Period.

The Liferay API supports user deletion. If you had used the Lifeline API, users would have been removed and your index etc. would be fine.

Okay, I know that it has to come in the form of a little aggressive or something, but it is necessary. The whole Liferay system depends on that data, so at any time when you manually emphasize the data, it probably breaks the system. If you dig through the actual process that Liferay API does for a user's extinction, you will see that there is only a small part of "Delete from user_ where ..."

I always tell people new ones just forget that the database is in existence. This is definitely your database, not yours, and does not mess with it.


Comments

Popular posts from this blog

import - Python ImportError: No module named wmi -

Editing Python Class in Shell and SQLAlchemy -

c# - MySQL Parameterized Select Query joining tables issue -