Closed ninjapapa closed 5 years ago
Since get_content_list
have to use spark context, if might be better to make it a SmvApp
method.
conn
instance. From user experience, they are acting on a connection.get_content_list
as a function with keyword args **kw
so that other connection types can define other filter params.Or maybe pattern should be an attribute of that connection....
probably should have said "might not have" instead of "will not have". Hive will have pattern but other future connection types may not have that concept.
pattern should probably stay with the get_content_list
. cleaner than splitting the content filter criterion between two places (in constructor and in getting content list).
Also, we may want to use pattern to filter out large connection lists as user type in (rather than our usual case of getting all items and filtering the in-memory list)
Will get everything without the pattern match.
Client code: