Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question on EntityCache #61

Open
agazzarini opened this issue Apr 12, 2016 · 8 comments
Open

Question on EntityCache #61

agazzarini opened this issue Apr 12, 2016 · 8 comments

Comments

@agazzarini
Copy link

Hi,
this is more a question than an "issue".
I'm new to Silk, I'm just trying to change a bit the simple example in order to fit my use case (interlinking a file of triples with some external datasets).

Now, the very first time I run Silk.execute() with reload = true everything works and produces some links. I see two folders under $HOME/.silk/entityCache/Interlink@id

  • source
  • target

where, I suppose, Silk caches the source and target resource lists.
Now, after

  • changing a bit my source file (i.e. changing some literals, adding some triples)
  • running again Silk.execute() with reload = false (i.e. I don't want to reload the target dataset because it's huge)

I got the same exact results. My question are:

  • if I want, for each invocation, change the source, do I have to run Silk with reload = true?
  • Is there a way for retaining only the "target" entity cache?

Many many thanks
Andrea

@afeliachi
Copy link
Contributor

Hi Andrea,
Unfortunately you have to reload if there is any changes in the source or the target, I had the same issue once, and yes by activiating the reload, both source and target are reloaded :(
But by looking into the code I think this can be easily changed

@agazzarini
Copy link
Author

Hi @afeliachi,
many thanks for your response.

I'm not sure, as I'm a Silk newbie, if it makes sense to have that as a feature or not.

@afeliachi
Copy link
Contributor

I think if it's really doable, it would be a great feature, especially in cases like yours when datasets are huge.

@afeliachi
Copy link
Contributor

I suggest you add an "idea" flag (label) to this issue if possible.

@agazzarini
Copy link
Author

I cannot edit the issue attributes. Are you able to do that?

@afeliachi
Copy link
Contributor

me neither. I'm not sure but I think it's up to the members of the project only.

@agazzarini
Copy link
Author

So that means we have to become members of the project :)

On 14/04/16 13:00, afeliachi wrote:

me neither. I'm not sure but I think it's up to the members of the
project only.


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#61 (comment)

@afeliachi
Copy link
Contributor

that would be better :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants