Multiple dll files for collection report

jon_elwood 2017-04-12 11:56:25 UTC #1

I noticed that in the Funnelback/admin/reports/ directory there are multiple dll files created - one for each time the analytics job is updated. Is there a reason for this?

Is it a support interface to query the sqlite db directly rather than going through the REST API? I did have a look at the DB schema and actual noticed that my connection to the DB prevented the analytics job from completing successfully (assume a temp DB is created and then overwritten on top of the reporting db) - so it looks like this isn't the best way to query reporting data.

gordongrace 2017-04-12 14:50:39 UTC #2

I noticed that in the Funnelback/admin/reports/ directory there are multiple dll files created - one for each time the analytics job is updated.

Are you only seeing these .dll files during the time the analytics job is updating?

Is it a support interface to query the sqlite db directly rather than going through the REST API?

This is not an officially-supported method, no. Only the APIs and the Marketing Dashboard UI are regarded as 'official', providing a separation between the interfaces and the underlying analytics datastore.

gtran 2017-04-13 00:49:49 UTC #3

Hi Jon,

The DLLs are created automatically by SQLite. What version of Funnelback are you running? In more recent Funnelback versions, it has been changed so the the libraries are deleted at the end of the update process.

Hope this helps.

Thanks,

~Gioan

jon_elwood 2017-04-13 06:06:54 UTC #4

A new dll file is created each time the reports are updated. I upgraded to 15.10 yesterday so ran another update to the analytics this morning - it still created a new dll. Is it ok to delete these? My concern would be that at 700K each these would rapidly fill up the disk.

gtran 2017-04-13 07:00:45 UTC #5

Oic...

I just tried this on one of our older windows servers and received the following:

Is this what you are experiencing too?

If it is, I'll raise a ticket with our RnD team to invest this further.

jon_elwood 2017-04-13 07:29:51 UTC #6

Yes - thats exactly what I see - except I get 2 dlls created for each generation so after a couple of regeneration of reports I have over 20 dlls now.

Let me know if I can provide any more information to help with the investigation.

gtran 2017-04-18 03:30:47 UTC #7

Hi Jon,

I have raised an internal enquiry and will let you know as soon as I find out more.

Thanks,

~Gioan

gtran 2017-04-19 23:22:26 UTC #8

Hi Jon,

I have raised this with the products team so that it can be addressed in upcoming releases. In the meantime, I can confirm that it is safe to delete these dlls after the reports have finished updating.

Hope this helps.

Thanks,

~Gioan

jon_elwood 2017-04-20 05:58:03 UTC #9

That's great - thanks for confirming.