I don't see the value we can add here. 
For example, does a Range query on URL make sense? 

If it's only for breaking the string into two subfields at index time, it can 
be done by a plugin like the mapper attachment. Although, I'd prefer using 
logstash for example to do that before sending the index request to ES.


Just my 0.05 cents here :)

-- 
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr


Le 31 juillet 2014 à 18:39:33, [email protected] ([email protected]) a 
écrit:

Maybe it would help to implement a new ES data type for URI/URL?

Usage example:

POST /test/test
{
    "url" : "http://127.0.0.1:80";
}

Jörg


On Thu, Jul 31, 2014 at 4:56 PM, Chris Neal <[email protected]> wrote:
Hi Jorg,

Here's an example:

An ip field named as 'host' in mapping.
               "host": {
                 "type" :"ip"
               },

Then I add below to ES
POST /test_index/test
{
  "host":"127.0.0.1:80"
}

ES returns this error
{
   "error": "MapperParsingException[failed to parse [host]]; nested: 
ElasticsearchIllegalArgumentException[failed to parse ip [127.0.0.1:80]]; 
nested: NumberFormatException[For input string: \"1:80\"]; ",
   "status": 400
}

If I only post IP without port like this
POST /test_index/test
{
  "host":"127.0.0.1"
}
ES return success.

Does that help explain the issue?
Thanks!
Chris


On Wed, Jul 30, 2014 at 4:35 PM, [email protected] <[email protected]> 
wrote:
Can you give an example what you mean by IP ports?

Transport protocols like TCP has ports, but IP (Internet addresses) is used to 
address hosts on a network.

Jörg



On Wed, Jul 30, 2014 at 11:02 PM, Chris Neal <[email protected]> wrote:
Hi all,

I'm trying to use the ip type in ES, but my IPs also have ports.  That doesn't 
seem to be supported, which was a bit of a surprise!

Does anyone know of a way to do this?  Or does it sound like a good feature to 
add support for to this type?

Thanks!
Chris
--
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/CAND3DpgEWdxZcaFe1wmSWtjRfXqxvUC0vbq8bfE0mC7DusS_%2Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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/CAKdsXoFKah6pkCWgKZYASM%3DfxyBq8waPQjyCBHj2aZaAeyiRwQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
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/CAND3DpjhbQunFsT8gi0bspkNDmj9u5kOyhohoAuEX20P0rcBkQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
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/CAKdsXoHkTDvuqYVFBy-L-WvgWA9NjeiHBAuj%2BmmiLW%3DJkn1jgQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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/etPan.53da728f.23f9c13c.f0d0%40MacBook-Air-de-David.local.
For more options, visit https://groups.google.com/d/optout.

Reply via email to