Thanks Tony. I was using gedit on a Linux box. Since I got my delete to work, I'm hoping to upgrade to Version 1.0 and then avoid using curl once my indices are created. I have to keep some proof of concept apps running so I'm trying to only break one thing at a time....
I just started feeding from Logstash, which is very nice, but I'm doing intermediate processing on the records before inserting them into Elasticsearch using the Java API. Thanks for your help. On 02/20/2014 10:49 AM, Tony Su wrote: > Hi Terry, > Just a comment on your "linefeeds and tabs" problem... > > My guess is that you're working on Windows. Plenty of text editors on > Windows insert invisible characters that can screw things up. > > But, I've found that the opposite is true in the *NIX world, few text > editors do that sort of thing. > > So, the general recommendation probably would be to find a text editor > that doesn't do that sort of thing or change OS where your choices will > more likely work. > > I've also found that JSON formatted statements can be executed in some > console environments, like *NIX bash(maybe not Windows console, I > haven't tried), so strictly speaking linefeeds and tabs aren't always an > issue. But, if you need to remove those linefeeds and whitespaces, there > are a ton of freeware and online tools to remove those (I use them to > minimize HTML pages and javascript)... so you can have the best of both > worlds, compose in JSON, then remove whitespace for execution. > > Re: indexing based on timestamp, you might take a look at the Logstash > apache log parser, it's done automatically by default an index is > created based on each day. > > HTH, > Tony > > > On Thursday, February 20, 2014 6:15:43 AM UTC-8, Terry Healy wrote: > > Yes, I am still running 0.90. Sorry, but I find the interaction via > curl > with complex json to be be awkward; I lost a lot of time experimenting > with possible syntax by cutting and pasting trials, only to find that > linefeeds and tabs in my formatted text were causing it to fail. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/elasticsearch/Xl6U_HHf1MQ/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/cb9134c1-8d7d-4987-9f69-f7ebd37b4a99%40googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "elasticsearch" 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/elasticsearch/53063F7E.9000606%40bnl.gov. For more options, visit https://groups.google.com/groups/opt_out.
