-
Notifications
You must be signed in to change notification settings - Fork 661
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
User Behavior Insights implementation for Apache Solr #2452
base: main
Are you sure you want to change the base?
Conversation
We have newer approaches such as the FileStoreAPI and the PackageManager.
… testing works with json query
I'd love to review here, but I think I need some more starting information either in a ref guide page or a JIRA, I'm kind of lost right now... |
Yeah... I'll go ahead and write up some ref guide docs! And finish the demo .bats script ;-) |
Usually, features like these are discussed in the dev@ list, or in JIRA or a SIP. |
This is definitely draft mode code... I opened it as a PR just to be able to track the work, and once it gets a bit furthur, I plan on opening a proper discussion about it. Module? Solr Sandbox? A Component? A full blown package? So many fun options... |
I am having some second thoughts about the idea of logging ubi queries to disk... Why? Any real use case you want them to go somewhere. Plus log4j is a pain to touch... So... May just rip that part out. You want to log to disk? just write a streaming expression ;-) |
We can stream to wahtever we want, a local log file, a Solr collection, s3, etc!
Description
I am working with other folks, especially Stavros Macrakis (macrakis@gmail.com), to come up with a solution for understanding what users are doing in response to search results. We have great visibility and understanding of an incoming query, what we do with it, and then what docs are sent back. We do NOT have a way of tying that search to then what does the user do next, and if the following query is connected to the original one.
Many teams lean on GA or Snowplow or custom code for tracking click through, add to cart, etc as signals, but nothing that is drop dead simple to use and open source.
Solution
User Behavior Insights is a shared schema for tracking search related activities. There is a basic implementation for OpenSearch and this is a version for Apache Solr.
Tests
Bats test to demonstrate the end to end use of UBI.
Checklist
Please review the following and check all that apply:
main
branch../gradlew check
.