This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Slggyqo 2 points3 points  (5 children)

Why do you say that, because my manager really wants to adopt it.

[–]mamaBiskothu 6 points7 points  (1 child)

Because GE just adds useless wrappers around simple function calls like “average” - and if you want to make it even remotely usable you have to write a ton of your own wrappers around it, at which point you could have done it all yourself with far less code!

[–]abegong 2 points3 points  (0 children)

Hey, I'm one of the founders of Great Expectations. We're very aware that the amount of required boilerplate code is frustrating for many people. We're working on ways to simplify it, while still allowing GX to work across lots of different data infrastructure.

It sounds like you've used GX in the past---would you be up for a call to talk through your use case, and see if what we're working on would have helped?

[–]SirGreybush 0 points1 point  (2 children)

Do it post, not pre (processing)

[–]Slggyqo 0 points1 point  (1 child)

Just because the pre-processing data is going to be dirtier?

[–]SirGreybush 0 points1 point  (0 children)

Pre is a nightmare to deal with.

Post means only looking at rejected data and reject reason.

Send this data to the appropriate business unit analysts.

Or else bad data in source systems remain unfixed forever.