[I] After turning on `blocking`, the search-meilisearch plug-in cannot search for answers to new questions. [incubator-answer-plugins]

["aaro-n (via GitHub)" <gi...@apache.org>]

aaro-n opened a new issue, #70:
URL: https://github.com/apache/incubator-answer-plugins/issues/70

   # system introduction
   Answer version: 2.2.5
   Answer plug-in: the latest version of the plug-in repository
   Running method: Build Docker image by yourself, with plug-in
   search-meilisearch ：1.2.5
   
   ## Build Dockerfile
   ```
   FROM apache/answer as answer-builder
   
   RUN apk --no-cache add \
       build-base git bash nodejs npm go && \
       npm install -g pnpm
   
   RUN answer build \
       --with github.com/apache/incubator-answer-plugins/search-meilisearch \
       --with github.com/apache/incubator-answer-plugins/cache-redis \
       --with github.com/apache/incubator-answer-plugins/storage-s3 \
       --output /usr/bin/new_answer
   
   FROM apache/answer
   
   COPY --from=answer-builder /usr/bin/new_answer /usr/bin/answer
   RUN chmod 755 /entrypoint.sh
   
   VOLUME /data
   EXPOSE 80
   ENTRYPOINT ["/entrypoint.sh"]
   ```
   ## Problem description
   
   After the search-meilisearch plugin is configured normally, the meilisearch search function can be used (new questions and replies to questions can be searched), but when `blocking` is turned on, the content of new questions can be searched, but replies to the corresponding questions cannot be searched. When `blocking` is not turned on, both questions and answers can be searched.
   
   ### Summary
   
   When the search-meilisearch plugin is turned on with `blocking`, answers to new questions cannot be searched.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@answer.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org