Paweł Róg

JVM GC logs format depends not only on JVM version but also JVM settings used to start JVM. We can look here to get inspirations: https://github.com/chewiebug/GCViewer/tree/develop/src/main/java/com/tagtraum/perf/gcviewer/imp An example for G1...

- For initial dump Logagent probably needs to `ls` a bucket and read all files - For new data Logagent probably has to subscribe to SNS

I think a periodical check is no-go. A bucket can have thousands, tens thousands or hundreds of thousands of objects and `ls` will not be fast enough.

As far as I see there are all INFO logs getting to the file but indeed when you try `LOG_LEVEL=debug` then it turns out that DEBUG messages go to stdout...

My point was that actually everything works as far as I could see on my machine. Are you sure there were any warnings or errors that you expected to see?...

Sorry, I'm a newbie when it comes to immudb. Just saw a message and decided to share my thoughts.

@SimoneLazzaris are you sure what's needed is a custom field that should be used as a document ID or maybe it's worth keeping the only allowed primary key field as...

I don't have full context where this particular cache is used but in general this is a common and good approach to use RW locks for caches. When you mention...

The problem is related to a way how the index key is created during the upsert. https://github.com/codenotary/immudb/blob/master/embedded/sql/stmt.go#L981-L999 First of all the ingredients of the index are encoded. For varchar type...

That's what I get this ``` $ avahi-resolve -4 --name homeassistant.local Failed to resolve host name 'homeassistant.local': Timeout reached $ avahi-resolve -6 --name homeassistant.local homeassistant.local fe80::ce52:7b89:2ca5:ebe2 ``` But then after...