I'm currently doing a bulk process and I'm about 7% done, but the database has already doubled in size! rdf_data_calais_node is to blame. Is this a bug or should I expect my database to grow to be over 100GB? This table is what makes calais_marmoset tick correct?

Comments

febbraro’s picture

febbraro commented
Status: Active » Closed (won't fix)

Yes, this is currently an issue, most with the RDF module and it's storage model. All of this RDF that is generated and stored creates a massive rdf_data_calais_node table. You can disable the local saving of RDF on the Calais Node Settings screen and truncate that table and you should be fine. The only thing effected from that will be the auto discovery RDF URLs. (http://www.example.com/node/123/calais/rdf) the rest of the integration via taxonomy (and Marmoset) will still work fine.

AntiNSA’s picture

AntiNSA commented

Can you explain to me in detail the disadvantages of disabling the rdf to be stored locally? Will tat effect seo or anything else?