Bug when running "then" nested frequency distribution with redaction.

[samaybar]

I have noticed this error before, when trying to to a "then" nested frequency distribution. I believe it arises when the "then" target returns redacted results.
See error below, and you can get config file here: http://bit.ly/1J0xbtr

16:31:05.419Z  INFO SE-PYLON-exporter: Using config file: politics2
16:31:05.422Z  INFO SE-PYLON-exporter: New OperationsEngine created with concurrency: 3
/Users/saybar/Dropbox/DataSiftShare/sra-ds-dev/SE-PYLON-exporter/lib/OperationsEngine.js:91
        (data.analysis.redacted === false) ?
                      ^
TypeError: Cannot read property 'redacted' of undefined
    at OperationsEngine.fn.cache (/Users/saybar/Dropbox/DataSiftShare/sra-ds-dev/SE-PYLON-exporter/lib/OperationsEngine.js:91:23)
    at /Users/saybar/Dropbox/DataSiftShare/sra-ds-dev/SE-PYLON-exporter/lib/OperationsEngine.js:72:22
    at Object.callback (/Users/saybar/Dropbox/DataSiftShare/sra-ds-dev/SE-PYLON-exporter/lib/OperationsEngine.js:115:9)
    at next (/Users/saybar/Dropbox/DataSiftShare/sra-ds-dev/SE-PYLON-exporter/node_modules/async/lib/async.js:801:43)
    at /Users/saybar/Dropbox/DataSiftShare/sra-ds-dev/SE-PYLON-exporter/node_modules/async/lib/async.js:32:16
    at Request._callback (/Users/saybar/Dropbox/DataSiftShare/sra-ds-dev/SE-PYLON-exporter/lib/OperationsEngine.js:130:9)
    at Request.self.callback (/Users/saybar/Dropbox/DataSiftShare/sra-ds-dev/SE-PYLON-exporter/node_modules/request/request.js:368:22)
    at Request.emit (events.js:110:17)
    at Request.<anonymous> (/Users/saybar/Dropbox/DataSiftShare/sra-ds-dev/SE-PYLON-exporter/node_modules/request/request.js:1219:14)
    at Request.emit (events.js:129:20)
    at IncomingMessage.<anonymous> (/Users/saybar/Dropbox/DataSiftShare/sra-ds-dev/SE-PYLON-exporter/node_modules/request/request.js:1167:12)
    at IncomingMessage.emit (events.js:129:20)
    at _stream_readable.js:908:16
    at process._tickCallback (node.js:355:11)

[haganbt]

Config:

        "freqDist": [
            {
                "name": "candidate_by_region",
                "target": "fb.author.region",
                "threshold": 10,
                "then": {
                    "target": "interaction.tag_tree.political.candidate-lastname",
                    "threshold": 10
                }
            },
            {
                "name": "region_by_candidate",
                "target": "interaction.tag_tree.political.candidate-lastname",
                "threshold": 10,
                "then": {
                    "target": "fb.author.region",
                    "threshold": 10
                }
            }
        ]

[haganbt]

Thanks @samaybar. I will see if I can recreate.

[haganbt]

@samaybar can you provide the index hash? It does not redact on my test instance.

[samaybar]

CS_3: hash: f95597fdb5b3bfe20ac425e81b8b32ed

On August 18, 2015 at 1:39:10 PM, haganbt ([e-mail]) wrote:

@samaybar can you provide the index hash? It does not redact on my test instance.

—
Reply to this email directly or view it on GitHub.

[haganbt]

@samaybar thanks for the input here. Error messages from PYLON were not being handled correctly for custom nested queries. f2d134e checkin fixes that. The API was actually returning:

ERROR SE-PYLON-exporter: Unsupported CSDL: Invalid CSDL

This appears to be caused by the hyphen used within your tag names. It appears PYLON does not support those as part of a filter and yet it does as a target. I will notify support of this bug.