tracker issue : CF-4205342

select a category, or use search below
(searches all categories and all time range)

CFINDEX action="status" not working in CF2016 or CF11

| View in Tracker

Status/Resolution/Reason: To Fix//BugVerified

Reporter/Name(from Bugbase): Jack D. / ()

Created: 09/30/2019

Components: Text Search, Solr Integration

Versions: 2016

Failure Type: Non Functioning

Found In Build/Fixed In Build: 2016.0.03301771 /

Priority/Frequency: Normal / All users will encounter

Locale/System: English / Windows 10 64 bit

Vote Count: 2

Problem Description:  Attempting to check the status of a SOLR collection does not work.

Steps to Reproduce:
<cfindex action="status" status="sinfo" collection="myCollection" /><cfdump var="#sinfo#" />

Actual Result:
This results in an error: "Variable SINFO is undefined."

Expected Result:
A CFDUMP of the STATUS results.

Any Workarounds:
None that I am aware of.



Ignore the last part of the title. I _do_ realize that status was added in CF2016 and does not exist in CF11. My bad.
Comment by Jack D.
31478 | September 30, 2019 03:55:10 PM GMT
CORRECTION: Just noticed it was introduced in CF10. smh
Comment by Jack D.
31525 | October 02, 2019 02:36:44 PM GMT
Bueller.. Bueller.. Bueller..
Comment by Jack D.
31582 | October 10, 2019 03:28:03 PM GMT
Component: Text Search : Solr Integration is clearly NOT correct. Don't even know how that got there. That's not what I chose.
Comment by Jack D.
31727 | October 29, 2019 02:42:13 PM GMT
Just curious as to the timeline on fixing this. I'm trying to write a process that will check the status of a collection, and if it's being indexed, will not index; otherwise it will.
Comment by Jack D.
31844 | November 21, 2019 02:28:01 PM GMT
Not trying to be that annoying guy, but I could really use an update on the timeline for fixing this. Project is progressing nicely, but this not being fixed will put it on hold. Please advise.
Comment by Jack D.
32054 | December 20, 2019 05:06:49 PM GMT
In case others come upon this, I will note first that a discussion of this was opened on the CF forums a week before this bug report was filed. And second, in that discussion I have added a comment today clarifying why I think we will ultimately learn that what is "to fix" here is not to get what Jack wants (the status of whether a collection is being indexed or not), but instead either a correction to the error message shown (to explain that the syntax being used is not supported), and/or a correction to the docs to better clarify why that is so. See my comment for more detail (and any responses, if folks disagree with my assertions):
Comment by Charlie A.
32055 | December 30, 2019 06:59:29 PM GMT