RemoveAsync doens't remove item from the Database.

[orchardc]

The following code doens't remove item from the Database.
await _contentManager.RemoveAsync(contentItem);

Physically remove contents from the database - is it even possible with API? Otherwise the database is growing very fast if not removable.

Any suggestion?

[hishamco]

Orchard Core is using soft delete, so no the content is not physically deleted

[Skrypt]

You can clean those records manually by using YesSQL directly like this : _session.Delete(existingContentItem)

[jtkech]

The IndexingTask is not an index table mapped to an index provider as the other ones, look at the IndexingTaskManager that updates this table by using explicitly a new transaction

This table is used by the lucene worker feature (need to be enabled) through a background task this to update lucene indexes based on the content item ids in this table, but only for the new ones that was updated

To do this, the table Id column is used as a cursor, we have a lucene.status.json in which we save per lucene index the last Id that was updated, so that the lucene worker knows that it needs to take into account all records whose Id > last Id.

So if the lucene worker feature is not enabled, this table is only updated but never used. If the feature is enabled, normally the worker will not try to re-index a given content item id in a given record whose Id < last Id in the json file

Hmm, but if you remove lucene.status.json, it may try to restart from the beginning, didn't try it but i think it would not fail

Otherwise, to remove the related records you would need to do it explicitly on this table

[orchardc]

@jtkech, thanks for the information, very helpful.

What I found is: although the Delete and Create new record works (thanks for your guys help!!)

After new records created, the Lucene Search doesn't work - I think it's because indices not built yet.

Is it possible to programmatically rebuild the Lucene Indices? Just want to trigger it immediately after records creation.

[jtkech]

You can try to use the LuceneIndexingService scoped service, needs a reference on OC.Lucene
See what the LuceneIndexingService does in its ResetIndex() and RebuildIndexAsync() methods

[orchardc]

It works well, thank you @jtkech , my only concern now is the IndexingTask table will ever-growing, which might impact performance.
I think it should be deleted as part of the _session.delete() process.

[jtkech]

Or a contentManager HardDeleteAsync() that would call handlers, one of the handler being implemented by the OC.Indexing module to remove the related item from the IndexingTask table.

[orchardc]

I think OC should proivde a way to remove (physically) content records from the DB.

Looking into tables: there might only be 5 tables which contains content:

AliasPartIndex
AutoroutePartIndex
ContentItemIndex
Document
IndexingTask

[Skrypt]

This will be available after the Audit Trail module will be merged. The idea is to be able to see every changes that has been made on a content item. For elements "soft deleted" we could have a "recycle bin" which would allow to remove the items completely or restore them.

[ShaneCourtrille]

@Skrypt Is there a work item for permanent deletion now that Audit Trail is in?

[Skrypt]

None yet. It is up for grabs by anyone interested.