I've caused myself a lot of headaches in the last 24 hours! Each time I attempt to upgrade from 6.x-2.2 to 6.x-3.0 the update hangs and after, say, 10 minutes I shut it down.

1. Is the upgrade somehow (seems unlikely) modifying all previous posts' Calais data, which could explain such a delay?
2. When I do cancel the update I generate an error in my logs surrounding gid, which naturally I haven't thought to save, so as to reproduce here. But it does hose the database, and I;'ve had to rollback (a miserable experience)
3. Fwiw, the upgrade of the RDF module was smooth
3. The upgrade to 6.x-2.2 was pretty smooth, though this error was thrown:

Table 'rdf_data_calais_node' already exists query: CREATE TABLE rdf_data_calais_node ( `did` INT unsigned NOT NULL auto_increment, `uid` INT unsigned DEFAULT NULL, `created` INT unsigned DEFAULT NULL, `gid` INT unsigned DEFAULT NULL, `sid` INT unsigned NOT NULL DEFAULT 0, `pid` INT unsigned NOT NULL DEFAULT 0, `oid` INT unsigned DEFAULT NULL, `tid` INT unsigned DEFAULT NULL, `lang` VARCHAR(12) DEFAULT NULL, `data` LONGTEXT DEFAULT NULL, PRIMARY KEY (did), INDEX gspo (gid, sid, pid, oid), INDEX gpos (gid, pid, oid, sid), INDEX gosp (gid, oid, sid, pid) ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in /home/science/public_html/cms/includes/database.inc on line 515.

Where things stand: I have 2.2 successfully installed on a production site, and am gun-shy about attempting a further upgrade.

Anyone else experience an update hang, and how did you get around it?

Comments

smazsyr’s picture

smazsyr commented

If a person were to resign themselves to this situation, how would they go about thoroughly uninstalling an earlier version of OpenCalais, so as to start fresh from 3.0?

febbraro’s picture

febbraro commented
Title: Update to 6.3 hangs » Update to D6 3.0 hangs
Assigned: Unassigned » febbraro

Hello there. Yes the upgrade process is modifying all previous Calais data. I am updating the data structure to allow for more features and flexibility and as such I had to move things around etc. If update.php is failing you can run all of the queries by hand and then update the system table so it knows what the schema number is.

Let me know if you need more info or pointers.

smazsyr’s picture

smazsyr commented

I appreciate the info. That's asking a whole lot from a Drupal user, though. Modifying 20,000 entries, each of which may have a handful of terms, is a pretty clunky/brute approach. As I've never managed to get through a full bulk update before a timeout error, I suspect you're dooming a lot of people (or at least those with a large number of nodes) from giving up on OpenCalais. Just my 2 cents.

febbraro’s picture

febbraro commented

I understand your frustration. There are very few ways to migrate your data structures in an efficient manner so I do what I can. What I hope is that those people that find value in the work we are doing will work WITH us to make it better. These updates are not required to be run via Drupal and PHP, they can rather easily be extracted and run directly on mysql avoiding the php timeout, etc. I can extract those into a SQL script to run directly if that would help. However, I do agree that is a lot of work for the untrained user, but what other options are there? As services and technology evolves so must the underlying data structures. I'm sorry if they are giving you headaches,

As for bulk update, there are plans to fix that too so that they can be picked up where they are left off in case of a timeout or other such interruption.

All patches to help us refine the functionality are welcome. :)

febbraro’s picture

febbraro commented
Status: Active » Closed (works as designed)