2

We are using SI4t for elastic search in pour project. We have created a module under deployer extension to push the data into the Elastic Search.

  1. TBB is working fine
  2. indexed search data generating properly
  3. Push data into the Elastic Search is also working fine.

But the page is published along with the indexed search data in to the database. As a result we are unable to get the content of the page.

Update

Here are the sample of page.html after publishing the page using that TBB

<!-- <INDEXED DATA> { Search  data } </INDEXED DATA> --> { DD4T json data of the Page }
  • Here are the sample of page.html after publishing the page using that TBB - <!-- <INDEXED DATA> { Search data } </INDEXED DATA> --> { DD4T json data of the Page } – Sayantan Basu May 7 '15 at 17:47
  • Hi - which jar file are you using - did you download the latest version? Would it be possible to post an entire transaction as DEBUG log? And did you make any customizations for Elastic Search ? – Raimond May 7 '15 at 19:12
  • Thanks for the reply. I am checking the latest version now. I will let you know If I face any issue later. – Sayantan Basu May 8 '15 at 4:58
2

If the SI4T storage extension is working correctly then the index data would be removed from the content stored in the broker database. The fact that this index data is still in there indicates a problem with the storage extension. Perhaps your Elastic Search indexer implementation is causing an exception which does not prevent indexing, but stops the index data being stripped out. If this is the case then there is probably something in the logs to indicate a problem - can you post/link to a full debug log when publishing a single page?

Note that there is an open issue to support adding index data in JSON format, to prevent this from being a blocking issue in implementations that publish content/data in JSON format, however the fact remains that something is going wrong in the deployer if this index data remains in the content stored in the broker DB.

  • Hi Will I am checking with the new version of jar file. I will let you know if I faced any issue after that. – Sayantan Basu May 8 '15 at 5:43
1

Will in this case we are using the old version of SI4T. I have now deployed the new jar and tested it again. Everything is working now. Thanks for the help.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.