Member since
05-17-2016
190
Posts
46
Kudos Received
11
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1105 | 09-07-2017 06:24 PM | |
1459 | 02-24-2017 06:33 AM | |
2010 | 02-10-2017 09:18 PM | |
6494 | 01-11-2017 08:55 PM | |
3807 | 12-15-2016 06:16 PM |
12-09-2016
10:09 PM
1 Kudo
Hello All,
LZO compression codec is enabled on HDFS and we are writing to HDFS using PutHDFS. We have run into the issue as in this question. Workaround to remove the LZO specific line from the core-site works fine.
However, is there a way that we can still use LZO codec with NiFi PutHDFS. The compression codec section of this document does not have specifics around NONE, AUTOMATIC and DEFAULT. Could someone share more information around this?
Thanks,
Arun
... View more
Labels:
- Labels:
-
Apache NiFi
11-18-2016
01:19 PM
Thanks @Matt Burgess. Currently I am handling this using a Javascript, similar approach to what you described. I wanted to confirm there is no other way. For simpler structures, I managed to extract the key values using Regex, but for deep nested keys, I was forced to use ExecuteScript.
... View more
11-17-2016
11:27 PM
Hello All,
While working with the QueryCassandra processor, the resultant JSON does not look fine for user defined types. Is there any workaround for this?
For the below CREATE TYPE first.fullname (
firstname text,
lastname text
);
CREATE TABLE first.users (
id uuid PRIMARY KEY,
name frozen <fullname>,
direct_reports set<frozen <fullname>>
); INSERT INTO first.users JSON '{
"id" : "62c36092-82a1-3a00-93d1-46196ee77204",
"name": {
"firstname": "person4",
"lastname": "4"
},
"direct_reports": [
{
"firstname": "person1",
"lastname": "1"
},
{
"firstname": "person2",
"lastname": "2"
},
{
"firstname": "person3",
"lastname": "3"
}
]
}'; The resultant JSON has all the User defined types converted to a single string as in the attached screen capture. Result for an Evaluate JSON Path expression results[0].direct_reports[0].firstname was directed to unmatched since the JSON result was not matching the expected JSON format.
... View more
Labels:
- Labels:
-
Apache NiFi
11-11-2016
04:43 PM
Rather than using \u0001 can you try \cA for the control A character?
Reference : http://www.regular-expressions.info/nonprint.html
"Many regex flavors also support the tokens \cA through \cZ to insert ASCII control characters. The letter after the backslash is always a lowercase c. The second letter is an uppercase letter A through Z, to indicate Control+A through Control+Z. These are equivalent to \x01 through \x1A (26 decimal). E.g. \cM matches a carriage return, just like \r, \x0D, and \u000D. Most flavors allow the second letter to be lowercase, with no difference in meaning. Only Java requires the A to Z to be uppercase."
... View more
11-11-2016
04:33 PM
2 Kudos
Try this ${dateNum:toDate("yyyyMMddHHmmss"):format("yyyy-MM-dd HH:mm:ss")}
Where dateNum is 20161011075959 (yyyyMMddHHmmss) which on formatting changes to 2016-10-11 07:59:59 (yyyy-MM-dd HH:mm:ss)
... View more
09-13-2016
04:24 AM
@Rajkumar Singh, okay got it. One more related question - On which node should I be placing the fair allocation xml file?
... View more
09-13-2016
03:54 AM
@Rajkumar Singh, does that mean that setting the class to org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler does not take into effect?
... View more
09-13-2016
03:45 AM
Hi All,
Is there any reference doc for configuring pre-emption is YARN Fair Scheduler?
... View more
Labels:
- Labels:
-
Apache Hadoop
-
Apache YARN