We are planning to implement search history for our users using the Analytics API as shown in this example.
Given search queries will be tagged then by user, for example like so user:unique_id, and that we have millions of users and growing, the question we had was:
is there a limit to the number of tags that can be stored/managed in EAS ?
You should be able to use tags this way.
It should not be a problem at search time, the analytics.tags can contain random string values.
The Search API should act just the same as if the analytics.tags only contain values from a very strict/limited set of values. The analytics.tags values have no effect for the Search or Click APIs.
The only problem might be that you might hit some limitations of the Analytics page for that engine.
For example the Analytics page has a tag filter which will show a limited number of tags.
You should still be able to use Analytics API to query the analytics events and filter them by tags.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.