4 ms·
not sure. part of the benefit of the use of client libraries is that I can make sure private data stays private - 'crawlable' content is going to make me have
by mgkimsal 16y ago
not sure. part of the benefit of the use of client libraries is that I can make sure private data stays private - 'crawlable' content is going to make me have to format it in such a way as to make sense to the crawler, and deal with making sure it's not accessible.
do you have a way around that? or am I missing something?
- zachfier 16y agoWe were actually considering both an initial crawling mechanism so you can "just go", and a very simple REST API for adding, updating, and deleting existing documents in the index. So you would be able to have both a 0-60 approach for getting your already-public-facing content into a sub-second search index, and also the ability to granularly submit document batches. As far as security is concerned, one assumption is that if your content is already crawlable, it's not private. That said, it would be trivial to implement a mechanism for keeping private data private - and even public data from being indexed (i.e. with a meta tag.)