Closed GoogleCodeExporter closed 9 years ago
One small detail omitted:
Linux environment has BFSIT amp installed:
alfresco-bulk-filesystem-import-1.1.amp
Windows environment has latest code from Mercurial.
Original comment by ehar...@ziaconsulting.com
on 7 Feb 2012 at 7:59
Can you retry using /vol/opt/alfresco everywhere you used /opt/alfresco? Java
doesn't handle symlinks very well and I suspect that might be what's causing
the issue.
Original comment by pmo...@gmail.com
on 14 Feb 2012 at 6:57
Peter, I retried without the sym link (updated dir.root in
alfresco-global.properties as well) and everything works fine on the Linux
server. Interestingly, the Windows environment works equally well with or
without the sym link.
Maybe the documentation should be updated to warn users of this?
Original comment by ehar...@ziaconsulting.com
on 16 Feb 2012 at 8:42
It's a new issue, so I wasn't aware of it until now. That said, I've linked
this ticket into the troubleshooting page
(http://code.google.com/p/alfresco-bulk-filesystem-import/wiki/Troubleshooting).
I'll also leave this issue open, as I still consider this behaviour a bug,
despite the fact that there's a workaround.
Original comment by pmo...@gmail.com
on 16 Feb 2012 at 8:56
PS. It's no surprise it works on Windows, as NTFS doesn't support symlinks,
only hardlinks (junctions), which are fundamentally different. I suspect
hardlinks would also work on Linux, although they're not normally used as they
have other challenges.
Original comment by pmo...@gmail.com
on 16 Feb 2012 at 8:59
Original comment by pmo...@gmail.com
on 16 Feb 2012 at 10:05
On Mac OSX I was unable to reproduce this issue. Creating a symlink to the
source folder in the contentstore results in a streaming import. The symlink
is dereferenced to get the "true" path, which is then detected as being outside
the contentstore, resulting in a streaming import.
I'll need to test this on Linux to see if it's filesystem specific.
Original comment by pmo...@gmail.com
on 17 Jan 2013 at 7:44
As part of fixing issue #114 the dereferencing of the symlink has been removed.
This means that symlinks in the content store are detected as being within the
content store and result in an in-place import.
Original comment by pmo...@gmail.com
on 18 Jan 2013 at 6:10
Original comment by pmo...@gmail.com
on 7 Feb 2013 at 7:33
Original issue reported on code.google.com by
ehar...@ziaconsulting.com
on 7 Feb 2012 at 7:49Attachments: