Heads up:
Seems like there's a pretty severe remote code execution vulnerability
[1] in Log4J. Basically any application that uses log4j and that allows
user input to be injected into a logging string is susceptible. This
probably includes Solr.
Further interesting discussion on Hacker News
We are trying to index documents for a collection. This worked in Solr 3.6.1,
but running this search under Solr 8.10.1 generates the below error.
multiple values encountered for non multiValued field
Any help would be appreciated, and feel free to ask if you need further info.
smime.p7s
Descr
Thank everyone for the input, it’s been a productive conversation!
Jason and I are planning on another hack day Jan 7th to take some of the
feedback, and work more on how our spike can help meet some concerns/show
promise, so we’ll report back then!
We’re planning on zooming during US East Coas
