Skip to content

Tajo jdbc thrift interpreters - #73

Closed
khalidhuseynov wants to merge 8 commits into
apache:masterfrom
khalidhuseynov:tajo-jdbc-thrift-interpreters
Closed

Tajo jdbc thrift interpreters#73
khalidhuseynov wants to merge 8 commits into
apache:masterfrom
khalidhuseynov:tajo-jdbc-thrift-interpreters

Conversation

@khalidhuseynov

Copy link
Copy Markdown
Member

This is for decoupling Tajo-jdbc and Tajo-thrift interpreters.

TODO

  • Rename Tajo interpreter explicitly into tajo-jdbc
  • Add tajo-thrift interpreter
  • Implement getProgress() for tajo-thrift interpreter, by @bzz
  • Learning Zeppelin architecture and handling unexpected problems
  • Implement cancel()

Comment threadtajo-thrift/pom.xml Outdated

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is old version number, after ZEPPELIN-65 AKA #59 and after ASF incubation policy version identifier for all artifacts should include -incubating and now looks like '0.5.0-incubating-SNAPSHOT'

@bzz

bzz commented May 13, 2015

Copy link
Copy Markdown
Member

@khalidhuseynov build fails, can you fix it please?

@khalidhuseynov

Copy link
Copy Markdown
MemberAuthor

Triggering CI Build

@bzz

bzz commented Sep 25, 2015

Copy link
Copy Markdown
Member

Shall we update or close this one, after #39 ?

it's confusing now: I think we need to have separate PRs:

  • rename existing from tajo -> tajo-jdbc
  • add tajo-thrift (w/ description what needs to be done on the tajo side to get it working)

@felixcheungfelixcheung mentioned this pull request Oct 25, 2015
egorklimov pushed a commit to Tinkoff/zeppelin that referenced this pull request Sep 18, 2019
…tuator.fix to V_1.0.0
* commit 'ee1392278082ea8793745c2d8d91ea4e914d6220':
[ZP-000] interpreter_queue without auth
[ZP-000] fix actuator problem
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@khalidhuseynov@bzz