SQLSTATE[42S22]: Column not found: 1054 [#1405040]

Comment	File	Size	Author
#1	1405040-1.patch	2.47 KB	nick_vh

Comment #1

he/him

Ghent

commented 17 January 2012 at 10:38

Status	File	Size
new	1405040-1.patch	2.47 KB

Does this help? I assume you are using another database type?

Log in or register to post comments

Comment #2

nick_vh

he/him

Ghent

commented 17 January 2012 at 10:39

Status:

Active

» Needs review

Log in or register to post comments

Comment #3

chrisssi commented 17 January 2012 at 13:20

Hi Nick_vh

thank you for this patch. I've patched the apachesolr.index.inc and after that I cleared again all Caches.

Then I added a node type = article. After that I still saw Remaining 0 Elements under Apache Solr Search Configuration and in the log file was an entry

Cron runs with apachesolr_nodeapi_mass_update() for ....IDs 495

where ID 495 = ID of this last added article.

But only the warning resists - no Errors (like above).

After another Cron the Indexed Items were counted +1 so the new Index Entree has been added to the Index. (fine!)

:-)

So the patch is working. But I'm not sure what I can do about the still existing Warning from Apache Solr.

Can it be ignored or is there anything a noob like me can do?

Log in or register to post comments

Comment #4

nick_vh

he/him

Ghent

commented 17 January 2012 at 14:03

I can't seem to reproduce the notice so I'd love some more information. Can you tell me what database type you are working on and possibly can you give me the english version of those warnings?

Log in or register to post comments

Comment #5

chrisssi commented 17 January 2012 at 15:00

The Database for the Drupal CMS is

MySQL - MyISAM (v 5.1.58)

on ubuntu Server 11.10
+ PHP (v 5.3.6-13ubuntu3.3)

The Java Server for Apache Solr is a

Tomcat 7.0.23 with Solr 3.5.0

on another ubuntu Server 11.10.

The Message is:

Type: Apache Solr
User: Anonymous (not verified)
Location: http://www.mysite.com/cron.php?cron_key={cron_key}
Message: On cron running apachesolr_nodeapi_mass_update() on nids {IDs_of_all_added_items_since_last_cronjob}
Severity: Warning

Hope these Infos help a bit. Allthough the Warning appears, the IDs of the mentioned Items disappear after the cronjob. So only the IDs of newly added Items where included in following Warning after next cron.
Before using your patch the List of IDs of the Non-indexed Items mentioned in the Apache Solr Warning accumulated because of the SQL Error.
Sorry I can't better describe it....

Btw when deleting an Item is working properly i think.
After deleting a node I see the Number of Pending Deletions directly under the Settings of Apache Solr.

Log in or register to post comments

Comment #6

nick_vh

he/him

Ghent

commented 17 January 2012 at 15:25

Ah, I see now. This is actually perfectly ok behavior. Nothing to worry about.

foreach ($node_lists as $nodes) {
    watchdog('Apache Solr', 'On cron running apachesolr_nodeapi_mass_update() on nids @nids', array('@nids' => implode(',', array_keys($nodes))), WATCHDOG_WARNING);
    if (!apachesolr_nodeapi_mass_update($nodes)) {
      // Solr query failed - so stop trying.
      break;
    }

You can safely ignore it!

Log in or register to post comments

Comment #7

chrisssi commented 18 January 2012 at 09:15

Thanks for your help!

A last question - Is it possible to make the Counter for Pending Updates / Remaining (when new nodes are posted) again working?
But it's a "nice-to-have" so if not it's not a Doomsday !

:-)