StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20273096
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-28T18:53:15.673
FavoriteCount
0
LastActivityDate
2013-11-28T18:57:19.537
LastEditDate
2013-11-28T18:57:19.537
LastEditorUserId
1265154
OwnerUserId
819977
ParentId
16739802
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
We recently hit this problem with a <code>threadsafe: false</code> project, and were able to resolve the issue by changing how were were importing the <code>context</code> module. Kevin explains the issue well in <a href="https://code.google.com/p/appengine-mapreduce/issues/detail?id=127" rel="nofollow">this bug report</a>. <blockquote> kevin.mo...@gmail.com Maybe this will help someone else, but I was seeing this issue and just figured it out for my use case. In our project, we have the mapreduce library in subfolders "libs/external/mapreduce" and not the root of our project. The library imports context (among other things) from itself as <code>from mapreduce import context</code>. So to make it work we are using import manipulation like so: <pre><code>import os, sys sys.path.append(os.path.join(os.path.dirname(__file__), 'libs/external')) </code></pre> However, in a few places in our code we were still importing context like so: <pre><code>from libs.external.mapreduce import context </code></pre> This will actually cause context to get imported twice and <code>mapreduce.context.Context._local</code> will get set twice, thus having two different instances of <code>thread._local</code>. When <code>Context._set</code> is called to store the context for later retrieval in a mapper function or something, it will be using the original <code>thread._local</code> instance. Later when our mapper module imports context again, it gets a new <code>thread._local</code> instance. When we were then <code>calling context.get()</code> it was returning the new instance which didn't actually have the context: <pre><code>AttributeError: 'NoneType' object has no attribute 'mapreduce_spec' </code></pre> Switching all our imports to <code>from mapreduce import context</code> fixed it for us. </blockquote>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGoogle python map-reduce library returning a NULL context
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USalko
UserOwnerUserId
1. USMatt Faus
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.