[jira] [Commented] (YUNIKORN-990) DocSearch Migration

["Chen Yu Teng (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/YUNIKORN-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17499819#comment-17499819 ] 

Chen Yu Teng commented on YUNIKORN-990:
---------------------------------------

update:
After fixed path in algolia crawler, searchbox in yunikorn website is work now.
!WrongPath.png!!image.png!

> DocSearch Migration
> -------------------
>
>                 Key: YUNIKORN-990
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-990
>             Project: Apache YuniKorn
>          Issue Type: Task
>          Components: website
>            Reporter: Weiwei Yang
>            Assignee: Chen Yu Teng
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 1.0.0
>
>         Attachments: WrongPath.png, image-2022-02-24-09-17-28-741.png, image.png
>
>
> h1. DocSearch is migrating!
> h1. 
> With DocSearch, we put developers needs first, so we always try to improve their experience with our tools. We teamed up with our beloved Algolia Crawler to provide a better platform for you to:
> * Access to the full Algolia Platform - Explore additional products and features for free
> * Better collaboration - Invite and manage additional team members
> * Power and flexibility of the Algolia Crawler - Previously only available to paid enterprise customers, it provides the ability to customize and refine your indexing like never before
> * Work on your schedule - Schedule or trigger crawls based on your demands from the Crawler interface or the GitHub action
> * Advanced tooling - The Crawler interface includes a live editor to maintain your config and allow you to test your search results with DocSearch v3
> h1. What do I need to do?
> h1. 
> We tried making the migrations as smooth as possible, so all you have to do to migrate your yunikorn index to our new infra is:
> # Create an Algolia account with your email address (the one that received this email)
> # Join your own Algolia application (the invite is valid 7 days, please contact us if you need a new one)
> # Update your DocSearch frontend integration with your new credentials: (ASK PPMC)
> You can also read more about the migration on our documentation or contact us at docsearch@algolia.com or on Discord
> h1. Can I still use my old credentials? When do I need to migrate by?
> h1. 
> Old credentials and indices will still be available, but crawl jobs will be stopped 3 months after you've received this email.
> h1. Can I still use the legacy DocSearch scraper locally?
> h1. 
> Yes, the configs and the scraper will still be available, but not maintained.
> h1. How can I configure/update my new Crawler?
> h1. 
> After you've created your Algolia account and joined your Algolia application, you can visit the Crawler interface and configure your crawlers!
> For any informations regarding your DocSearch configuration, please visit our new documentation. If you were familiar with the legacy DocSearch scraper and configs, please read our key parity page.You can also read more about the Algolia Crawler on the Algolia Documentation.
> h1. Do I need to trigger my crawls manually?
> h1. 
> No, your crawls are already scheduled to run once a week, but you are now able to trigger a new one whenever you want!
> h1. I'm not using this index/these credentials anymore
> h1. 
> Keep in mind that DocSearch is a community project, please let us know if that's the case so we can disable it.
> Read more in our migration guide



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org