I deploy these files from svn repository. since logging.yml is under
subversion there is a .svn/text-base/logging.yml.text-base file. ES load
this file ends with text-base and assumes its a json format. a
org.elasticsearch.common.jackson.core.JsonParseException is raised. Is
there a way to tell es that my file is yml not jason?
We have the same problem is reading .svn/text-base/logging.yml.text-base
and fails to setup logging.
I think the loading logic should be a little more restrictive. Loading
everything that starts with "logging." including files in "hidden"
directories, is a little bit too much.
I fixed it with mounting an empty directory over the .svn directory. It's
no problem for us since we mount it over NFS and manage it on another host
(without the .svn empty directory). You could add that to the initscript
(mount before starting and umount after the start), if you need to use svn
on the host itself.
But imo that's a dirty hack and should be dealt with in elasticsearch (at
least ignoring "." directories).
We have the same problem is reading .svn/text-base/logging.yml.text-base
and fails to setup logging.
I think the loading logic should be a little more restrictive. Loading
everything that starts with "logging." including files in "hidden"
directories, is a little bit too much.
I fixed it with mounting an empty directory over the .svn directory. It's
no problem for us since we mount it over NFS and manage it on another host
(without the .svn empty directory). You could add that to the initscript
(mount before starting and umount after the start), if you need to use svn
on the host itself.
But imo that's a dirty hack and should be dealt with in elasticsearch (at
least ignoring "." directories).
Ok, moving/copying is also a way to solve it. But in my case it wouldn't
work since we have a readonly nfs mount.
I opened an issue:
Let's see what happens.
On Thursday, October 9, 2014 5:08:19 PM UTC+2, Jinyuan Zhou wrote:
What i did is renamimg logging.yml to something else and then at startup
time I "copy" the contents to logging.yml
Thanks,
Jack
Jinyuan (Jack) Zhou
On Thu, Oct 9, 2014 at 2:28 AM, Daniel P. <thetux...@gmail.com
<javascript:>> wrote:
We have the same problem is reading .svn/text-base/logging.yml.text-base
and fails to setup logging.
I think the loading logic should be a little more restrictive. Loading
everything that starts with "logging." including files in "hidden"
directories, is a little bit too much.
I fixed it with mounting an empty directory over the .svn directory. It's
no problem for us since we mount it over NFS and manage it on another host
(without the .svn empty directory). You could add that to the initscript
(mount before starting and umount after the start), if you need to use svn
on the host itself.
But imo that's a dirty hack and should be dealt with in elasticsearch (at
least ignoring "." directories).
We have the same problem is reading .svn/text-base/logging.yml.text-base
and fails to setup logging.
I think the loading logic should be a little more restrictive. Loading
everything that starts with "logging." including files in "hidden"
directories, is a little bit too much.
I fixed it with mounting an empty directory over the .svn directory.
It's no problem for us since we mount it over NFS and manage it on another
host (without the .svn empty directory). You could add that to the
initscript (mount before starting and umount after the start), if you need
to use svn on the host itself.
But imo that's a dirty hack and should be dealt with in elasticsearch
(at least ignoring "." directories).
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.