Hi Henri, I think there's missing an information in the doc: you also need to change standalone.value.maxsize for standalone or ingress.value.maxsize for distributed. Keep in mind that storing images in a time series database is far from being optimal.
Regards, Fabien On Monday, February 17, 2020 at 3:06:26 PM UTC+1, henri laurent wrote: > > Hi, > > I am trying to save images in a standalone Warp10-2.4.0 database. > I have no problem saving images with a base64 encoded size less than > 100000 bytes (see attached photo_loaded_successfully.txt file). > I cannot save larger images, I am getting a (Value too large for GTS ) > error message while uploading my image with curl (see attached > photo_failing_to_load.txt file). > > I saw in the documentation ( > https://www.warp10.io/content/03_Documentation/03_Interacting_with_Warp_10/03_Ingesting_data/02_GTS_input_format) > > that the "Maximum size is linked to the max.encoder.size" parameter. > I modified standalone.max.encoder.size in the > /warp10-2.4.0/etc/conf.d/00-warp.conf file. from the default 100000 to > standalone.max.encoder.size = 400000 > and restarted Warp10. > > I still can't save pictures. > > Can you help? > > Thanks, > > Henri > > -- You received this message because you are subscribed to the Google Groups "Warp 10 users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/warp10-users/4e8d1e24-6749-402e-92b6-e2b49ac531c0%40googlegroups.com.
