Hi Dylan,

Indexing such data as flatten works for my case. I've checked that
documentation before and this is similar to my need at documentation:

"world": [{"hey": "there"}, {"tree": "apple"}]

However, I don't know what will be the keys at indexing time. Such
configuration is handled via this at documentation:

...
{
  "type": "path",
  "name": "world-hey",
  "expr": "$.world[0].hey"
},
{
  "type": "path",
  "name": "worldtree",
  "expr": "$.world[1].tree"
}
...

However, I can't define parseSpec for it as far as I know. I need something
like working as schemaless or defining a RegEx i.e?

Kind Regards,
Furkan KAMACI

On Wed, Jan 9, 2019 at 5:45 PM Dylan Wylie <dylanwy...@gmail.com> wrote:

> Hey Furkan,
>
> Druid can index flat arrays (multi-value dimensions) but not arrays of
> objects. There is the ability to flatten objects on ingestion using
> JSONPath. See http://druid.io/docs/latest/ingestion/flatten-json
>
> Best regards,
> Dylan
>
> On Wed, 9 Jan 2019 at 14:23, Furkan KAMACI <furkankam...@gmail.com> wrote:
>
> > Hi All,
> >
> > I can index such data with Druid:
> >
> > {"ts":"2018-01-01T02:35:45Z","appToken":"guid", "eventName":"app-open",
> > "key1":"value1"}
> >
> > via this configuration:
> >
> > "parser" : {
> >         "type" : "string",
> >         "parseSpec" : {
> >           "format" : "json",
> >           "timestampSpec" : {
> >             "format" : "iso",
> >             "column" : "ts"
> >           },
> >           "dimensionsSpec" : {
> >             "dimensions": [
> >               "appToken",
> >               "eventName",
> >               "key1"
> >             ]
> >           }
> >         }
> >       }
> >
> > However, I would also want to index such data:
> >
> > {
> >   "ts":"2018-01-01T03:35:45Z",
> >   "appToken":"guid",
> >   "eventName":"app-open",
> >   "properties":[{"randomKey1":"randomValue1"},
> > {"randomKey2":"randomValue2"}]
> > }
> >
> > at which properties is an array and members of that array has some
> > arbitrary keys and values.
> >
> > How can I do that?
> >
> > Kind Regards,
> > Furkan KAMACI
> >
>

Reply via email to