I can't get it to
accept more than 4 custom fields, and it won't let me use the new CF10
custom field syntax for custom fields either (where you can do
something like catalogid_i versus custom1).
Just to follow up on this, I did figure out that the problem with the dynamic
custom fields
The one I'm frustrated with though is the status fields. They are
supposed to include a keywords struct and keywordScore when the
suggestions criteria is met
Just to follow up more on this, I continue to be frustrated trying to work with
the Solr on our CF10 install, it's almost like we
one thing to bear in mind, if you are using shared hositng. If any customer
on the server deletes their collection (i.e. deletes the files or folders)
this completely breaks SOLR for everyone else.
for this reason I would avoid using SOLR unless it will be running on
dedicated hosting.
Yes, this
one thing to bear in mind, if you are using shared hositng. If any customer
on the server deletes their collection (i.e. deletes the files or folders)
this completely breaks SOLR for everyone else.
for this reason I would avoid using SOLR unless it will be running on
dedicated hosting.
On Wed,
I'm working on an integration with Solr specifically to use it to help lookup
word suggestions for our searches. However, the cfsearch docs are definitely
driving me nuts. First, the type attribute doesn't seem to work at all in
CF10, even though it's clearly included in the documentation for
I'm working on an integration with Solr specifically to use it to help lookup
word suggestions for our searches. However, the cfsearch docs are definitely
driving me nuts. First, the type attribute doesn't seem to work at all in
CF10, even though it's clearly included in the documentation for
6 matches
Mail list logo
